3 ms·
I like the idea of pitching Ruby on Rails. It’s relatively easy to grasp and contains everything including the kitchen sink. The thing I’ll share is that I hav
by runjake 3y ago
I like the idea of pitching Ruby on Rails. It’s relatively easy to grasp and contains everything including the kitchen sink.
The thing I’ll share is that I have a day job and kids. I learned JavaScript and then started learning a JS framework.
The problem I had was that by the time I was able to become proficient in a framework, it was on its way out and there was some new thing.
I still do a lot of JS with Node and Express and Fastify but I’ve stopped bothering with further frameworks until I have a firm requirement for one.
- kirso 3y agoYeah, I think the safe option for employment is React. I would have picked up Rails, but I am not well-versed with Ruby despite knowing about the productivity of the stack.
- runjake 3y agoI don't think you're going wrong either way. It is worth checking out the job market around you and using that to ultimately decide. Around here, for whatever reason, Rails jobs seem to pay much higher than JS jobs. But, I know that's not true everywhere.
- kirso 3y agoInteresting! Thank you for that. I don't plan to become an "employed" dev - just want to build my own projects :) Curious what part of the world that is? I know in Japan Rails is big.