Twitter On Scala

machaut writes "Twitter, one of the highest profile Ruby on Rails-backed websites on the Internet, has in the past year started replacing some of their Ruby infrastructure with an emerging language called Scala, developed by Martin Odersky at Switzerland's École Polytechnique Fédérale de Lausanne. Although they still prefer Ruby on Rails for user-facing web applications, Twitter's developers have started replacing Ruby daemon servers with Scala alternatives, and plan eventually to serve API requests, which comprise the majority of their traffic, with Scala instead of Ruby. This week several articles have appeared that discuss this shift at Twitter. A technical interview with three Twitter developers was published on Artima. One of those developers, Alex Payne, Twitter's API lead, gave a talk on this subject at the Web 2.0 Expo this week, which was covered by Technology Review and The Register."

Stupid

[AKAImBatman]

They should have just used Java. Wait--

Good thinking,

[geekoid]

replace one language that wasn't tested on that scale and replace it with another one that wasn't tested on that scale.

Good thinking~

Oh look, twitter is down..again.

Scala? Not for me!

[bogaboga]

Scala is not for me I can confidently say. I am too old to learn a new [programming] language. The languages I know will suffice for now.

There is a saying too: "You cannot teach old dogs new tricks."

Aw, Java and Python had a baby!

[gpig]

Isn't she cute :)

Mod down

[Anonymous Coward]

OP is just a twitter sock puppet.

Re:Who gives a shit about twitter?

[FredFredrickson]

Wow I just realized what an angry old man I must sound like there. I didn't mean to be that harsh. I'm just don't like twitter, and spending time speaking about its technical *wonders* seems to be a waste of time, since I assume it's about 3 lines of code (Or should be), and mimics most highschool coding class students' first projects.

Wow, there I go again. So angry. I just quit caffeine, you must understand!

Re:Scala? Not for me!

[Anonymous Coward]

You know, at first I thought this post was off-topic, because it's an incredibly pointless life update that none of us could possibly care about.

Then I realized that the story is about Twitter, and suddenly I think it's the most relevant post so far.

Re:Should have used PHP.

[iluvcapra]

Well, it wasn't stable enough for twitter :D

Psht.

[kkrajewski]

I program in PDP-11 assembly, which is then translated into C, compiled into Java bytecode, and executed on a JVM. I call it Assemblacava, and it's the wave of the future.

Re:Should have used PHP.

[Achromatic1978]

I'd flame on, but I'm trying to compose myself after the fits of laughter that the phrase "lifestream transactions" brought on. Seriously?

Twitter should have used Perl

[Anonymous Coward]

Every scripting language tries to do what Perl does. None of them have CPAN.

I've tried repeatedly to use Ruby and RoR. For trivial projects, they are fine. Scalability may come, but Ruby GEMS needs to be rewritten in Perl to remove the HUGE memory footprint to maintain your GEMS. You all know what I mean.

Yep, perl is what Twitter needs.