It's a bummer this article starts out with a quote about Rails providing a bad OOP learning environment and then talks about the framework itself never touching on the learning of OOP again.

--

    "it's lead Rails developers to build huge, 
    monolithic models that are hard to test, 
    and violate SRP."

...Sounds like you need to structure your code better.

    "Have you ever seen a 200 line long 
    controller method? I have."

... What on earth are you talking about? This has nothing to do with rails. Structure your code better.

    "The whole idea of logic in templates 
    leads to all kinds of problems."

...Then don't put logic in your templates. Use helpers or logic-less templates.

    "MVC has served the web well... 
    ...But I think we're reaching its 
    limits"

...If the type of web app you want to make isn't best constructed with an mvc framework, don't use mvc. But honestly, I can't think of anyway to more blissfully implement a RESTfull webapp than with respond_to and resourceful routes.

    "This post is light on examples. 
    I want this to be the starting point 
    of a discussion"

...This exact discussion has been raging for years. Your only chance at gaining ground is through examples.

--

This brings me to: When is this post from? I feel like it's 5 years old and I've slightly been had.