4 ms·
Not to talk down Clojure, but it sounds like the real success here was being able to reinvent existing systems, and having a CTO willing to give you the space t
by untog 12y ago
Not to talk down Clojure, but it sounds like the real success here was being able to reinvent existing systems, and having a CTO willing to give you the space to do it.
After all, the majority of sites like this are getting data from <data store>, squeezing through <template> and delivering to the user's browser. The language you do that in will have a much smaller effect than, say, your caching strategy (particularly at a high volume site like MailOnline).
- calibraxis 12y agoConventional wisdom holds that rebuilding an old system is fraught with pitfalls. Executing is nontrivial and has zillions of decision-points where things could've gone radically differently. Evaluating impact of tool choice requires experience and is intertwined with other factors. My experience tells me that Clojure's use is significant.
- tim333 12y agoThe CTO talks a bit about the rebuild at his talk on using Node: http://youtu.be/HGH66JhUkis?t=8m59s http://youtu.be/HGH66JhUkis?t=8m59s The old system was 155,000 lines of Java and similar. The team before him tried to rebuild using J2EE and XSLT and failed to get anything working in 8 months of trying. They then reorganised and rebuilt the system in about 4000 lines of Clojure: http://youtu.be/HGH66JhUkis?t=16m3s http://youtu.be/HGH66JhUkis?t=16m3s
- poooogles 12y agoSounds like us, 150k lines of Java/Escenic. Can't wait to move away from that hell hole.
- seanmcdirmid 12y agoI remember an old article on Java3D: rewriting a C++-based system in Java3D led to an order of magnitude improvement in performance! Of course, the lessons they learned from writing the C++ system could be cleanly integrated into a fresh Java3D implementation, so the comparison was not honest at all.
- tensor 12y agoIt would have been nice to see the comparison with independent implementations in different languages. It's too bad that they didn't persist with that idea.
- delibes 12y agoI don't remember much about the node.js implementation. Some early experiments with Ruby were beset by problems the VMs - Ruby MRI vs JRuby vs Rubinius etc ... We also had strange performance issues on JRuby, but not sure we ever really tracked it down. In comparison getting Clojure running was easy. I felt so comfortable that I even tried emacs for a while (vim user) :P