I am a front end web developer. I mostly don't care what is going in backend and I just call the API endpoint to get my JSON blob. Recently I interested in lea

I am a front end web developer. I mostly don't care what is going in backend and I just call the API endpoint to get my JSON blob. Recently I interested in learning a bit of backend programming. I did start learning Node.js and Rails together. I hate Rails too. All Rails tutorials and guides are like reader knows everything they know. I feel it was easier before but now there is so much you need to learn to make a real world Rails app. Sure that Twitter clone is easy. But it gets hard when you want to make a bunch of "gems" work together. You need to know a lot of history of Rails in order to get it. I liked Node.js over Rails not because I know JavaScript better than Ruby, I never had problems writing or reading Ruby code. It's a beautiful language. The reason I love Node is that I know what is going on. There is not much unnecessary magic. I know it's not fair to compare a "framework" with a "whatever-we-call-node-js". But Node my points are: - Rails itself is very skinny that can't do much without gems - By adding multiple gems to make the framework usable you get into truble of making them work together. So if Rails wants to solve all my problems it should include all functionalities I (usually) want or if it tries to be skinny and light it should be like Node.js