Spell-check did though.

Tell that to the people that say AI will be doing all of our jobs in 5 years.

But it is a skill issue, just UI/UX design skill. Not software development skill.

Anywhere I’ve actually seen it used , assembler and assembly were pretty much interchangeable. Assembly code is probably technically correct, but you could be writing code for the assembler so nobody will actually be confused. Per your example, you might say “I wrote code in MASM,” to reference a specific assembler. Again nobody that’s actually worked with any of this would bat an eye at the usage.

What a lot of people forget is that in the early days of Linux there was no software that targeted it. Everything you would want to run on Linux was intended to run on something else like Solaris, BSD, AT&T Sytem V, SCO, AIX or something else. As a result, Linux APIs were the most generic flavor of Unix possible. Almost every thing meant for a Unix would compile and run on it and there was rarely a dependency problem.

I still miss that.

Even MS hates nmake. Visual Studio has had native support for cmake since 2017.

Computer programs need lots of separate pieces to operate together in subtle ways or your program crashes. With art on the other hand I haven’t heard of anyone’s brain crashing when they looked at AI art with too many fingers.

It’s not so much that AI can’t do it, but the LLMs we have now certainly can’t.

deleted by creator

One of these delivered the customer requirement: an egg. The other is still working on an egg incubation framework.

I work with Qt and that framework has preferences for avoiding a lot of modern C++. I generally agree that it makes better code.

Also, I started with C++ in like 1992 and some part of me still feels like templates are newfangled nonsense.

Any “customers” landed are going to be friends and family, if not just outright fakes invented by leo.