upvote
Lot of stawman arguments.
reply
Wouldn't be a authentic pjmlp comment unless they shit on C/C++ and/or praise Java/.NET with a bunch of straw-men :)
reply
How wrong you are, C++ isn't in the same league as C, Microsoft was right not wanting to keep updating their C support.

It was already outdated by the time Borland released Turbo C++ 1.0 for MS-DOS, and only got new wind thanks to GNU FOSS and their manifest to prefer C as the main compiled language for GNU projects.

Everywhere else outside UNIX, was going with a mix of C++ for OS frameworks, Apple, Microsoft, IBM, Be, Nokia, Epoch,....

Naturally given the option, between C, C++ and something else I might prefer that something else, however I managed a few interesting positions exactly due to my C++ skills, and interests.

So don't mix my preferences for C and C++ on the same basket.

reply
Wouldn't trade it for anything <3 Enjoy your Tuesday mate :)

> So don't mix my preferences for C and C++ on the same basket.

That mistake is mine indeed, I'll remember. Thanks, and I hope "no harm meant" was implicit :)

reply
Really?! That is how many in C circles, including your regular comments to my comments happen to be like.

Two measures two weights, in C versus other systems languages.

reply
Maybe provide a concrete example instead of making vague accusations. Or rather, please not, it is not a useful discourse. A productive response to my comment would be an insightful explanation of how byte-level access to memory objects is done in other languages.
reply
"When other languages have compiler specific extensions beyond the spec, it is a failure in their design."

This one of the failures of Linus T. with the linux kernel: he was not able to keep the assembly source code with plain and simple C code you can compile with a small and alternative C compiler (same failure for the glibc devs I think).

I don't blame him, he is already keeping the linux ABI stable, and pulling that off is something.

reply