News for hackers. Stuff that matters.
Re:Why I'm Productive in Clojure (2013) by yogthos on Sunday October 22, 2017 @09:15AM (#15526670)
I love it when people make a mess because they didn't really understand the problem initially, then rewrite it in something else and give all credit to the new technology they happened to be using.

When you rewrite a project it's always going to be a lot better, because you have a much better understanding of the problem being solved having done that once already.

Re:Why I'm Productive in Clojure (2013) by hellofunk on Sunday October 22, 2017 @09:44AM (#15526798)
Indeed, on anything serious I write it at least twice. Of course, using Clojure makes this easy since there is usually not a lot of code to rewrite. But after you get into something, you know details about what is needed that you simply cannot adequately predict beforehand in a lot of circumstances.
Re:Why I'm Productive in Clojure (2013) by imhoguy on Sunday October 22, 2017 @02:14PM (#15528117)
True, but only with small projects. Once initial creators of rather complex project leave then the mess begins. No language will save you from changing requirements, egos or best practices. Will your rewrite of inherited 200KLOC "is always going to be a lot better"?