Re:How To Identify A Lame Programming Job
by nickelplate on Thursday December 03, 2009 @10:11PM
(#975714)
What's wrong with using C++ in 2009?
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.
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++
All legacy code is a liability, and all code is legacy.
Re:How To Identify A Lame Programming Job
by prodigal_erik on Friday December 04, 2009 @04:41AM
(#976070)
To me "legacy" connotes flawed, not merely old. If a rewrite would end up slightly modernized but basically the same, what you have is an investment. If a rewrite would end up completely different because the old version doesn't meet the current requirements, what you have is a legacy problem.
Re:How To Identify A Lame Programming Job
by access_denied on Friday December 04, 2009 @02:20PM
(#976985)
You are distinguishing between "legacy" and "legacy problem" and thus rendering your own opening 'thesis as moot.
Re:How To Identify A Lame Programming Job
by prodigal_erik on Saturday December 05, 2009 @02:05PM
(#978428)
Sorry, what I was trying to get across is that I don't expect to hear "legacy" unless there's a problem.
Poor legacy code is a liability, and legacy code that leads to suboptimal technical situations (e.g. using C++ in 2009) is a pain.