The author uses how models are suggested to be used "the rails way" as an example for why it doesn't work anymore, talking about business logic in the models.

But in every framework I've used, the suggested way isn't how a technology is used in reality, in production. The tutorials are almost like a different framework entirely. Years ago as an Android dev the difference was shocking between what tutorials taught you and what was done in practice.

This doesn't technically detract from the author's point but it makes it moot - you just build in the current best practice way or the way that suits your needs, and that's how it often is with languages and frameworks.

Maybe that mismatch between how people are taught initially, or how the framework is intended to be used, is an inefficiency, in which case those who design frameworks should take note.

In the case of Rails I think "the rails way" is appropriate for certain style of apps, and not so much for Shopify etc scale apps.