Moving on from Rails sounds great until you try to build a serious web app with one of the alternatives. While I think that many of the architectural criticisms are valid, Rails demonstrates the primacy of ecosystem and strong conventions over language design and cs theory.<p>&#x27;Tomorrow&#x27;s&#x27; languages and frameworks would do well to take heed. Winning this war has as much to do with culture and marketing as algorithms and data structures.<p>Clojure, for example, is a much stronger programming language than Ruby on paper, but for a straightforward web app, you&#x27;ll likely spend <i>at least</i> twice as long to get something working--and while it will be based on better engineering principles, it will also take new engineers much longer to grok since it doesn&#x27;t follow any universal set of conventions.<p>With Rails, you end up in the weeds in the long run, but the alternatives put you in the weeds right off the bat (with the promise of eventual salvation). The reality of most product development (ymmv) is that the former is highly preferable to the latter.