[nickjj]

Yep and this is the problem. Initial library support isn't close to enough.

It needs to be extracted from a real project and then carefully groomed and enhanced based on real problems.

Otherwise you're just sitting there trying to invent something with no use case. You can't invent a beautiful API or account for edge cases that you don't even know exist.

This is why Rails will be around and thriving for another 10 years. Until something so drastic comes along that it fully disrupts everything we know about web development, I will still reach for Rails.

Right now all of these alternative solutions in other languages aren't offering enough benefits to even think about switching.

P.S., I'm not even a Rails fanboy. I use other techs too and tried to get on the bandwagon with Node back in the early days and did the same thing with Go. It took a long time to realize how much of an utter waste of time it is to chase the new shiny thing.