> Rails was a cool concept, just better implemented in other more performant languages.
Agree and disagree.
The first win of Rails-inspired systems is the idea of actually providing decent building blocks for building a large application instead of just throwing you a router and some HTTP tools like the Sinatra-a-likes do. (If I had a dollar for ever minute I wasted dealing with writing something any decent Rails clone would have given me for just-about-free... that'd describe about 25% of several jobs I've held. :P)
But the two biggest wins of running Rails specifically are having a major community's worth of software around it, and having a Very Expressive Language with which to build the rest of it. These let you save on developer time in a variety of important circumstances where dealing with complexity is much more important than dealing with performance (internal-facing applications, for one, or XYZ-management-systems).
Agree and disagree.
The first win of Rails-inspired systems is the idea of actually providing decent building blocks for building a large application instead of just throwing you a router and some HTTP tools like the Sinatra-a-likes do. (If I had a dollar for ever minute I wasted dealing with writing something any decent Rails clone would have given me for just-about-free... that'd describe about 25% of several jobs I've held. :P)
But the two biggest wins of running Rails specifically are having a major community's worth of software around it, and having a Very Expressive Language with which to build the rest of it. These let you save on developer time in a variety of important circumstances where dealing with complexity is much more important than dealing with performance (internal-facing applications, for one, or XYZ-management-systems).