If Rails, as of now, would&#x27;ve been a very fast framework, the post author would have never published such post, despite all the other &quot;defects&quot; he underpins.<p>Rails could eventually get very fast, but it can be frustrating that it&#x27;s not right now!<p>This is the same kind of problem of Ruby not having a proper x-platform GUI toolkit or binary packager: you have such a expressive and powerful language and still you feel you are limited by the lack of speed and tooling.<p>That&#x27;s why, IMO, a Ruby&#x2F;Rails dev frustration can explode in such a strong way at some point.<p>Sadly Ruby isn&#x27;t backed by a big corporation, so you can only wait for the language and frameworks to get more mature.<p>Personally I&#x27;ve dealt with this frustration by learning C#. It allowed me to overcome all the current limits of Ruby, while avoiding the Java ShitFactory. At the same it feels great to get back to Ruby when you want to explore ideas! It&#x27;s still an unbeatable tool for prototyping. Being aware that I have knowledge of another language, makes me feel better, less frustrated, and I browse Ruby weekly news with much less &quot;anxiety&quot; for a revolutionary Ruby improvement (but still I browse it because I know it will happen sooner or later!).<p>I&#x27;m quite sure that the OP after having vented with this post, and having found what for him is a solution, then he will peacefully embrace Ruby or Rails again under a different light (but again, I wouldn&#x27;t be so surprises to see big improvements soon, so maybe it could even be a better light!)