News for hackers. Stuff that matters.
Re:Taking C Seriously by aidenn0 on Thursday November 03, 2011 @12:35AM (#3190314)
I've consulted in the past on embedded projects. In my experience, maintaining a non-trivial body of C++ code is easily a factor of 2-10x harder than maintaining equivalent C code.

I have lots of reasons why this is true, many of which are specific criticisms about C++. There is one issue that is industry specific: Everyone working in embedded has either come from the bottom up (deep firmware in assembly or machine code) or the top down (Java in school), and when you get a dozen people where half of them treat C++ like "C with classes" and the other half treats C++ like it's Java, it's a guaranteed disaster.

Re:Taking C Seriously by cageface on Thursday November 03, 2011 @04:50AM (#3190873)
Then why doesn't somebody clue in Adobe, Ableton, Epic Games, Pixar, Valve, Google etc and get them to abandon their wicked C++-loving ways? If what you say is true in general then you could save a lot of the brightest engineers in the world a lot of headache.
Re:Taking C Seriously by gte910h on Friday November 04, 2011 @03:11PM (#3197335)
The reason why games are written in C++ is because the gaming industry was sold on the idea in the mid 90's and now all the tools are written in it.

For low level systems work, C++ can be considerably more difficult than C to organize and port large programs.

It isn't "C++ is always worse than C" it is "C is often better than C++ for a given task, depending on task"

Re:Taking C Seriously by aidenn0 on Thursday November 10, 2011 @06:58PM (#3222583)
Also, win32 is a C++ project. There are significant advantages to writing in the same language as the underlying platform.