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!
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.
Keeping that in mind, were those companies really burned by Rails or were they making lazy decisions and not being honest about what their plan was for their software?
Most businesses are technology agnostic - they don't care what we use, if, if we deliver robust technically sound solutions. But when they trust developers, who fail to deliver, they mark the technology choice as well, to avoid getting similar problems in the future.
Just to note, I'm a PHP dev who works in SEO, and have done for years, during the great SEO boom, so I know bad code and I know snake oil salesmen. But I think in about 12/18 months time, once all the charlatans have moved on, the ruby/rails devs left will be experienced, battle hardend legacy devs, and the respect will begin., much like the SEO industry now.
If a fair number of those executives learn too late about the technical limitations of Rails, they probably do feel burned, and word gets around.
Funny thing is a lot of the projects that were a mess because the devs could not manage the pressure the businesses put on them which made for some real bad decisions. The devs themselves were actually pretty good and knew the code base had gotten out of hand.
So now whenever someone says "oh this company wont use X because they got burned by those programmers" my internal alarms instantly start going off that the problem is more than likely the managers of the business.
Ruby is past it's hype and others are taking up the space. Node.js is very good at replacing Ruby for quick development and Typesafe's Play works better for Java shops.
A lot of companies got burnt on ruby related projects. Especially anything rails related. There is a steady pipeline of work right now for skilled developers to migrate services and code from ruby to go, Scala, java - basically anything else except ruby.
I have earnt quite well doing such gigs, although I tend do more erlang/elixir stuff these days.
I would always ask the clients what happened, and why they want to migrate rather than maintain or even build out their ruby code bases, and the answer was always the same - the developers in the ruby space were mostly sub-par. Often several degrees below java developers in terms of skill and ability. I would say it tallies with my experiences too.
It is also for this reason they are not using node js - because it was seen as the next shiny, all the half-devs from ruby jumped onto it, and the risk of crap codebases from the same amateurs is ever present.