Put differently, anybody that cares about performance, would probably not want to use it for that reason and therefore is not using it. Personally, I've had good experience dodging some of the performance and concurrency issues with jruby but still ended up replacing ruby with plain java in the end. Performance wasn't the key concern here but just the fact that ruby seems to require a lot of ever elusive discipline in order to keep some notion of architectural sanity. There's just something in the ruby community that causes ruby projects to self implode under the never ending monkey patching, silly hacks and type obfuscation. At some point replacing it completely with just about anything else becomes very attractive.
A recent problem with rails is that it only made sense as long as server side MVC was a thing. That notion is sort of dead now that we have client side apps doing their own MVC layers (react, angular, etc) along with such things as graphql, microservices and simple json APIs. It's just not as good as a match for development as it was 13 years ago.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Put differently, anybody that cares about performance, would probably not want to use it for that reason and therefore is not using it. Personally, I've had good experience dodging some of the performance and concurrency issues with jruby but still ended up replacing ruby with plain java in the end. Performance wasn't the key concern here but just the fact that ruby seems to require a lot of ever elusive discipline in order to keep some notion of architectural sanity. There's just something in the ruby community that causes ruby projects to self implode under the never ending monkey patching, silly hacks and type obfuscation. At some point replacing it completely with just about anything else becomes very attractive.
A recent problem with rails is that it only made sense as long as server side MVC was a thing. That notion is sort of dead now that we have client side apps doing their own MVC layers (react, angular, etc) along with such things as graphql, microservices and simple json APIs. It's just not as good as a match for development as it was 13 years ago.