News for hackers. Stuff that matters.
Re:How To Identify A Lame Programming Job by prodigal_erik on Friday December 04, 2009 @06:06AM (#976145)
It gives up all possible safety for performance gains that haven't mattered on the desktop for years. "volatile" is not enough of a memory model to write portable threaded code for I/O bound multicore machines. And it's missing an awful lot of modern conveniences that are painful or unreliable without language support: AOP, closures, currying, invariants, reflection, serialization, remoting, extensible syntax.
Re:How To Identify A Lame Programming Job by gaius on Friday December 04, 2009 @08:49AM (#976311)
Echoing the commenter above, people writing C++ in 2009 are laughing all the way to the bank.
Re:How To Identify A Lame Programming Job by HeyLaughingBoy on Friday December 04, 2009 @04:03PM (#977198)
I don't know about laughing all the way to the bank, but I would probably have more difficulty writing machinery control code in anything other than C++