[ribadeo]

No. However, Rails addresses many items on The List. Hence, it's worth using it as a checklist. In reality, things like cache-busting codes are pretty straightforward to write in <language of your choice> and choices about how to represent database entities and validate incoming data require contextual and experiential validation, one size (ActiveRecord) truly doesn't fit all.

One is well served to learn Rails for many reasons, but i would not start a green field 2025 project with any framework.

I have been burned by rapid development frameworks in the past, not Rails, but anyway, by now I've been rolling my own stacks for awhile, and it was mainly a question of language ecosystems.

Have a gander at Crystal Lang, BTW, and Amber and Lucky frameworks

[ultrarunner]

I'm building a trial balloon in Crystal right now, though not Amber or Lucky. They had their 1.0 release (1.15, even), but it does not feel ready for production. The documentation is not great, the gotchas are unintuitive, and the discussion feels like they're not sure what direction to take the language. The runtime (event loop, fiber scheduler, and garbage collector) dependency means there's plenty of "magic" involved, making it feel significantly more like a framework than a language. Maybe that makes sense if they're targeting the web. If you're on the fence about choosing an established framework like Rails, though, Crystal is not the direction to go yet.