News for hackers. Stuff that matters.
Re:Lisp is Too Powerful by wpietri on Sunday December 25, 2011 @11:41AM (#3391192)
Hmmm. I think I still maintain my preference for bad Java over bad Ruby. The AbstractSingletonProxyFactoryBeanImpl insanity is painful, but I feel like most Java problems can be solved with pruning shears. Ruby's metaprogramming, on the other hand, puts COMEFROM-style functionality into the hands of noobs, and its duck typing makes it very hard to answer basic questions about what the hell X is. In Java, I can always tug on something and figure out what it's connected to. But perhaps that's just a matter of my personal debugging style.

Broadly, though, I think you're right: it's irrelevant to the real problem. Java is the new COBOL because most large software development organizations are functionally insane. They can't tell good code from bad, and rig things in a way that bad code is almost guaranteed anyhow. So naturally they'd prefer a language in which bad code is merely painful, not fatal. Because that lets them cover up their failings for much longer periods.

My personal solution is yours: stop working with other people's shitty code. I'd like to see the problem solved across the industry, but focusing on language choice doesn't seem like it's getting us anywhere.

Re:Lisp is Too Powerful by raganwald on Sunday December 25, 2011 @10:55PM (#3392172)
Applying hordes of programmers to solving a programming problem always runs into limits governed by Conway’s Law:

http://en.wikipedia.org/wiki/Conways_Law