News for hackers. Stuff that matters.
Re:Where my mouth is by rayiner on Sunday September 15, 2013 @09:10AM (#6388965)
I feel precisely the opposite way. I used to work on developing network algorithms. Our simulations used C++. It was phenomenally unproductive, because in addition to the inherent difficulty of the problem, you had to deal with the limitations of the language. Its a pain to debug C++ in a straightforward "move bits around" app. Its even more painful to get distracted by stack smashing bugs when you're trying to figure out the emergent behavior of a complex algorithm.
Re:Where my mouth is by Mithaldu on Sunday September 15, 2013 @04:02PM (#6390111)
Which language would you have preferred? Most other languages where such bugs would be handleded by the language tend to be a lot slower. (I'm saying that as a Perl developer who occasionally has to write C because Perl won't cut it for a decent algorithm.)
Re:Where my mouth is by rayiner on Sunday September 15, 2013 @05:05PM (#6390331)
There are a host of languages > 20% as fast as C (Common Lisp, Haskell, Java). I would have preferred Common Lisp but would have settled for Java. Once you're within a factor of 2-3 of C, speed rapidly becomes less important than other things except in limited circumstances. I wouldn't write an h264 decoder in Lisp, but short of that...
Re:Where my mouth is by Mithaldu on Sunday September 15, 2013 @05:49PM (#6390442)
Ah, thanks for the answer. I was mostly curious since i work with things where algorithms need to perform in realtime, so even a factor of 2-3 is unacceptable.