I just started learning it this week and it isn't bad... However, there's quite a bit of setup, and it's a bit tricky at first.

Basically, a few years ago I thought it was easier to build my own framework in Golang, C, C++. I've also used PHP, Node and Flask from time to time. After doing all that, I had a pretty good understanding in how it all works, and can see the beauty in some of the way Rails works. I definitely think it'll keep growing and is worth learning if you're into web development.

It's not easy at all. I mean, if you are filling in the generated scaffolds, it may be easy. But when your coworkers start using all the nasty routing DSL tricks and the myriad of helpers, it stops being easy. Thing is, it's too big and rich for its own good, and let's not speak of the development practices it encourages.

> there is a steep learning curve

citing the parent

no that's bullshit, just do the rails tutorial online and you'll be good to go. OF course you need to know Ruby. Like with any other language, you can't just learn the framework.

It's easy if you stick with vanilla Rails. Where it gets complicated is if your team decides to use a different view language, a decorator gem, a factory framework, and a different testing framework. The more deviations from Rails proper, the higher the learning curve gets.

If a person know Git, HTML, JavaScript, and one server-side language, I can teach them enough Rails to build production apps in a few weeks. I've had a lot of success with that.

That is the problem with rails. It starts off easy when you are just making CRUDs and as the code grows bigger, you have to know a lot on how the framework works and that's where the learning curve hits you.