News for hackers. Stuff that matters.
Re:Talking to C Programmers about C++ [video] by pjmlp on Sunday September 25, 2016 @11:58AM (#12575846)
The same applies to the languages I listed, given the amount of years they have.

C++ main issue has always been C's compatibility and the C subculture.

The copy-paste compatibility was necessary to bring C developers over the fence to C++, with minimal changes to their tooling.

So C++ inherited all the flaws and UB from C.

Then many of those kept using C++ as plain C with Classes, which influences many of the design decisions regarding language semantics, specially given backwards compatibility as no one wants to repeat Python's error.

Having said this, although I enjoy playing with template metaprogramming, I hope never have to deal with SFINAE, declpspec and function return arrow syntax in production.

Re:Talking to C Programmers about C++ [video] by qwertyuiop924 on Sunday September 25, 2016 @03:01PM (#12576787)
...But that's not often how those languages are used.

And most of those "flaws" aren't flaws in C: They were deliberate design decisons. Arguably bad ones, yes, but they were made a reason. By C++, most of those decisions didn't have any reasons, or were actively against C++'s goals, if not C.

I know you hate C, but blaming C for C++'s problems is like blaming dogs for the monstrous dog demon that someone made with gene editing. C compatability was a bad idea, but you can't blame C for that. Also, it's overly baroque.

But yeah, I think we can all agree that complex TMP is kinda sucky.

Re:Talking to C Programmers about C++ [video] by pjmlp on Sunday September 25, 2016 @03:33PM (#12576960)
Those decisions are documented in "The Design and Evolution of C++".