Earlier quoted context omitted.
I think a major holdback for Ruby, is how tightly it is coupled to Rails. Comments like this show how the community, unconscious, ties them together too. I think for Ruby to truly thrive again, it must become more than 'the language rails was once written in'. I'm a Ruby developer. I don't particularly like Rails (but don't hate or avoid it either) and I'm more and more convinced that Rails is doing Ruby more harm th…
On the contrary, I think Rails continues to sustain the Ruby ecosystem. It's not like there aren't alternatives such as Sinatra and Grape for microservices. There are also plenty of non-Rails Ruby jobs. If you search for `ruby -rails` on Indeed.co.uk there are 1879 results so 1503 when you factor-out 10% for unrelated results.
There are really neat complete frameworks like hanami, padrino and grape (not sure how active they are, though) too.
My point was not that "its impossible" just that compared to other languages, the Rails framework is an Elephant In The Room.
Python is much larger than Pytorch, Pandas, Django or whatnot. Typescript was built for React mostly, but outgrew that rapidly. Javascript is no longer focused around on framework (like it was in jQuery times, if you consider jQuery a framework). Java-for-web often boils down to Spring, but Java is much, much more versatile than that.
With Ruby? There's chef, puppet, some sinatra, capistrano and then there is ... RAILS!