My time with Rails is up
I can&#x27;t take his opinions too seriously because his 3 central gripes, which he wrote extensively about, boil down to:<p>1) Too much complexity is hidden by simple interfaces<p>Those simple interfaces make programming enjoyable and don&#x27;t break, so...<p>2) Your app logic is going to be too tightly coupled to core Rails features like AR, helpers, controllers (&quot;your app is Rails&quot;)<p>Yes, you are in fact using the features of Rails when you use Rails. Is this actually a problem?<p>3) ActiveSupport. &quot;No actual solutions, no solid abstractions, just nasty workarounds&quot;<p>ActiveSupport has saved me bajillions of hours and never broke anything for clients. I wasn&#x27;t aware it was such a flawed library, if it is?<p>Rails is maximized for developer happiness by, among other things, making things simple (yes, which to a large extent means hiding complexity), giving you a bunch of Omikase core features that you can in fact use, and gives you a lot of sugary methods for handling things that are tedious. I understand people wanting to try other things and leave Rails, no problem with that, but his stated reasons reveal a lot more about him than about Rails.