Somehow I didn't have much to do with Ruby in my dev career.
First I worked at a dev shop that did PHP for years.
Just knew a few students at university who did internships with Rails and they came back pretty disenchanted, so I never considered it later.
Yeah, I wouldn't really advise anyone who doesn't already use Rails to feel like they need to get into it. Especially when you're well-versed in other fields that are way more hot.
But I think a lot of current Rails developers feel like they are supposed to move off for JS stacks or otherwise. It's just not the case. Rails is in a lovely mature state.
I'm using node by way of yarn and webpack but I never built a node app so I'm just using it as a tool.
I don't know exactly why but I've never felt the attraction.
Does it make sense? There are some technologies that, unless you end learning because it's required of you, you don't pursue.
Am I missing something? Surely, but there's also a limit on how many pieces of tech we need to learn to write web apps.
Depends on what you want to do.
If you build front-ends, you probably need Node.js as a tool.
If you build back-ends, you may use Node.js as the server, but you could also use Rails or something else.
Agreed. I dipped my toes in the GraphQL ecosystem and the "universe" keeps telling me I should use Node for that :-)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.