I&#x27;ve got my problems with Rails: routing is overly complicated, the asset pipeline can be tricky, and so on.<p>But Rails is very good at producing HTML and, in particular, partial chunks of HTML.  As the current thick-clients-in-javascript trend cools off (it&#x27;s happening, this was at the top of &#x2F;r&#x2F;webdev yesterday: <a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;webdev&#x2F;comments&#x2F;4iphv4&#x2F;12_year_of_progress&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;webdev&#x2F;comments&#x2F;4iphv4&#x2F;12_year_of_p...</a>) people are going to migrate back to HTML as a transport for web apps, using libraries like <a href="http:&#x2F;&#x2F;intercoolerjs.org" rel="nofollow">http:&#x2F;&#x2F;intercoolerjs.org</a>.  (Disclosure: I developed it)<p>Rails is well positioned for that.