Comments on: Twitter Scala/Ruby Drama

By: vaxorcist

vaxorcist — Tue, 09 Mar 2010 18:04:48 +0000

as we all know all too well… any failures related to an ROR project is due to insufficiently following the ROR ideology to the hilt…

Sorry, I must apologize, I’ve worked with a few ROR ideologues… PTSD…

but seriously… I’d love to know specifics, probably more specifics than the lawyers will let them tell….

By: Harry

Harry — Sat, 10 Oct 2009 16:44:46 +0000

maybe it’s because scala is much demonstrably faster than ruby AND can interoperate with Java code because it compiles to java bytecode on the JVM? Get over it. RoR is SOOOO 2005.

By: Duct Typing « fate = will && choice || circumstance

Duct Typing « fate = will && choice || circumstance — Sat, 26 Sep 2009 07:48:25 +0000

[...] system motivating a move to Scala. I mean we’ve heard this before and the whole thing got a lot of Ruby panties in a bundle when it first came [...]

By: Láďa

Láďa — Fri, 17 Apr 2009 17:04:41 +0000

Important thing is that Twitter is replacing Ruby code on backend only. Frontend is still written in Rails and Twitter folks said that Rails and Scala play nice together, see http://www.artima.com/scalazine/articles/twitter_on_scala.html
Ruby is failing badly when it comes to backend and I think that every experienced Ruby programmer knows this. Rest of Ruby crowd will have to find out

By: Amit C

Amit C — Wed, 08 Apr 2009 17:23:09 +0000

It is definitely a interesting programming topic to bring to others attention, that itself is worth it.

It was a minor comment, please ignore it.

Remi, Thanks for putting up the link again. I read it, pretty interesting from a historical POV. It ends up saying, there are many MQ systems now and the followup mentions Scala for type-safety among other things.

By: Parand

Parand — Wed, 08 Apr 2009 16:53:59 +0000

There’s been a lot written about the Twitter/Scala switch, and frankly I’m neither a Ruby nor a Scala expert, so I’m not well qualified to opine. From a first principle argument I’d say it is very likely that a reasonable solution can be created in Ruby, or found off the shelf, but it is also the case that certain tools and languages – in this case Scala – do lend them particularly well to certain domains – in this case messaging.

Did I manage to say nothing?

My main gripe is with the Ruby folks reacting to every defection and less than deifying word. Some people are going to like something else more than Ruby, so quit getting upset about it, learn from it, and continue making Ruby great. You can’t please everyone all the time, and the defensiveness is starting to sound like insecurity to me.

By: remi

remi — Wed, 08 Apr 2009 16:32:21 +0000

that said, the link you posted is a very interesting read!

http://unlimitednovelty.com/2009/04/twitter-blaming-ruby-for-their-mistakes.html

By: remi

remi — Wed, 08 Apr 2009 16:29:35 +0000

Agreed, I found this blog post because I was googling to find out about Twitter’s switch to Scala, why they did it, how they’re liking it, etc.

I’m mostly curious because I’ve been seeing the Fail Whale a lot lately, which I haven’t seen in *ages* :/

By: Amit C

Amit C — Wed, 08 Apr 2009 00:49:25 +0000

Hey Parand,

I would say another angle would be more useful, why the choice\decision between the two, some (maybe many) of us do not know\care about reaction to a decision…

Amit