[lucasfdacunha]

Yeap. I had the same feeling. If he never mentioned that he worked with Rails before I would understand not being familiar with the Rails concept of the "New" and "Edit" actions, but he mentions a lot of time throughout the video that he worked with multiple Rails backends and he doesn't even have familiarity with the most simple concept of Rails Controllers and Routes?

I felt that he has a bit of an agenda against DHH and I guess that's why he thrashes Rails as much as he did on that video.

[Lio]

Yeah this video is just cheesy strawman arguments. Make a claim that's not true then argue passionately about why it's a bad idea.

Like droning on about scaffolding without acknowledging that it's just get you going training tool that you're expected to grow out of almost immediately.

Or bemoaning that Rails is "framework" and so you're forced to use all of it. It's just reasonable defaults you can opt out of really easily. e.g. swap out ActiveRecord for Sequel or replace ActionController with GrapeAPI. Don't like backend rendering? Just remove it. You can pick only the bits of Rails you want via Railties.

Even going on about how you're forced to put business logic in models is pretty silly. It's right there in the Rails Guides how to keep models only for data access and move business logic into business logic into pure service classes. Don't like that? Use modules or engines or Trailblazer or any number of alternatives.