The issue with Ruby is that it is so tightly associated with simple architecture of Rails. Nothing wrong with Rails in itself, but for many complex projects that require architectural solutions Rails doesn't support, Rails + inexperienced devs usually results in spaghetti code.
Ruby is fine, but RoR is toxic.
A language without its framework is like a hammer without a nail.
I feel like switching stacks before actually getting work might do more harm than good and at this stage I'm not looking to contract.
I'm not saying anyone here is incorrect in their generalizations of Rails developers. I've obviously never seen the code they are criticizing. But they also aren't providing any useful information. Keep that in mind above all else. There will always be politics and disagreements. You're never going to make everyone happy and it would be a disaster to try to.
It's my understanding that the mood is simply that rails/ruby/node is toxic; its the same with what used to be SEO, they've all become UX snake oil salesmen.
As a Go dev, I'm crapping it that Go may be the next bandwagon jumped onto :( It kinda makes me glad when I see all those comments complaining about lack of generics!