the various full stack rubies are cute, but if i don't have grown up concurrency then i'm not interested.
A place for everything. Ruby's weak threading is a shame, but doesn't keep Ruby/Rails from being an exceptionally productive way to build and deploy small/medium web applications, and to bootstrap large web applications.
Don't call Ruby "bad" because it's worse than Scala at Scala's strongest points.
you had better get serious about staking out your turf on the jvm
Also, isn't that the whole point of this article? A lot of Rubyists are doing this right now.
without that i'm left wondering if the disagreement/disapproval comes from ruby advocates with no facts to back their arguments or people who think that underendowed "office space" jokes are a valid retort for ruby fans with no facts to back their arguements.
I guesss maybe I do have a case of the Mondays, but you have undergraduate class project garbage collection and worse threads. Go charge $300 dollars a seat for your motivational ruby seminar or something. Scrum's at 11am.
Now, first of all, it's entirely possible that the Ruby community as a whole doesn't care about getting into the enterprise. I don't pretend to speak for the whole community, and obviously (via the article), some do. Competing on the JVM may not be the best way to promote the language as a whole. As you've said, the space is getting crowded, and if Ruby bets its cards on being the dynamic language of choice for the JVM, and then misses its target, how would that look? I won't deny that JRuby is an awesome thing, as I personally would like to see Ruby used (almost) everywhere. However, it's not as if, say, PHP gets maligned because it's not 'enterprisy' enough. It does for totally different reasons, and well-deserved ones at that. But the language is doing quite well without being able to be run on the JVM.
As far as concurrency and garbage collection go, I think it's hardly fair to judge all of Ruby on 1.8.7. YARV holds quite a bit of promise, and just goes to show how with just a little bit of care, Ruby can be made to be on par with every other language out there. See the link below for the comparison between 1.9 and 1.8. Now, in a pragmatic sense, this doesn't affect things _right now_, but they do change the near future quite a bit. So yes, Ruby's concurrency and gc may not be the best, but it's not as if there's no improvement or work being done.
http://shootout.alioth.debian.org/u32q/benchmark.php?test=al...