You're going to incur the wrath for saying the silent part, but you're not wrong. People have the same 5 rails example corps every time someone says one of these two things:

- without rails nobody would use ruby

- without X corp, ruby's dead

Fact is, we're seeing less and less usage, and more and more distillation of the current userbase along the golden paths laid out by DHH.

Is it wrong for rails and thus ruby adoption to slow down? Not at all, people should use what they like, however I think Rails and Ruby are in this negative spiral where:

- rails is mostly needed for prototyping and crud apps

- this work is typically done by juniors

- rails devs are at this point largely seniors, not juniors

- rails devs pay the bills with other tech or by maintaining legacy rails apps.

There are startlingly few deviations from this, and either everyone majors in rails with a minor in javascript and C++ or they just get happy with their current gig and settle. I wish it weren't the case, but Ruby just hasn't done enough to differentiate itself from Rails, and when compared to neo-PHP or JS there's just not a lot of attractive parts of the golden path Rails provides. It's off-tune for this generation of choice and ubiquity.

We don't need that level of scaffolding anymore and in many cases there are other tools that handle that with more versatility.