I would generally prefer C, but that’s more , I suspect, from habit. Rust has innate garbage collection.
I think of C as for when you need very low level efficient code, and C++ for when you need a *lot* of very efficient code all in one language. Rust covers almost all of the situations you would use C today, and a lot of the C++ cases as well. Go has some of the C++ cases, but it’s pretty similar to the C# or even Haskell cases.
As a guy taught how to design languages, I find this interesting.
The critical thing you really do is define the problem you want to deal with and then select the methods, tools, resources, and supplies to do that task in the time frame, within the costs, and deal with the inevitable failures
you will encounter.
That is not coding.
It is called engineering.
A skill most all “High Tech” coders don’t have a clue about.
tech ping
Peruse later.
I don’t have a clue what this guy is talking about, but I found it an entertaining read. Lots of people who think they know how to write could learn something from him.
i prefer c/c++ for my server backend responding to network requests or to easily enable pub/sub strategies... all with an eye on performance.
the whole stack these days seems to be tending towards:
( c/c++ backend ) <—> ( protobuf messaging ) <—> ( javascript based web front end )
native frontend code seems to be going the way of the dodo, with chromium clients being the portable foundation for most native dev
thoughts?