21 ms·
It sounds like they've gone for "easy to develop" rather than "easy to maintain" but any app in the real world will spend 10-100x longer in maintenance mode tha
by gaius 13y ago
It sounds like they've gone for "easy to develop" rather than "easy to maintain" but any app in the real world will spend 10-100x longer in maintenance mode than active development.
Or more cynically, they are optimizing for billable hours, but only once the customer is locked in, having being beguiled by the low costs up front.
- j45 13y agoExactly. The emerging perpetual Rails re-factoring cycle is very Microsoft-esq in some ways -- the second you buy in, you'll keep buying if you keep using the software. To be fair, this is not a problem just in Rails. I see similar issues in the emerging JS world too, where everyone is re-inventing libraries for JS that have existed already for decades in other languages, only with new authors. Reminds me of F. Scott Fitzgerald's Gatsby quote a little sometimes. :) The strangest thing is after working in several worlds, I'm slowly finding myself looking to the JVM, and wondering if I'm crazy to be considering the Java world (albeit in the form of the JVM) that I was happy to run from after University. Jython, JRuby, Querus under one roof is a strange experience, I'm sitting on a foundation of some of the most performant, scaling libraries in Java.
- dredmorbius 13y agoWhat's that Gatsby quote if you don't mind?
- j45 13y ago"So we beat on, boats against the current, borne back ceaselessly into the past." http://www.sparknotes.com/lit/gatsby/quotes.html http://www.sparknotes.com/lit/gatsby/quotes.html
- dredmorbius 13y agoThanks. Nice.