twitter用scala构建高性能消息服务

这里有一篇关于Twitter使用Scala的详细报道：
http://www.artima.com/scalazine/articles/twitter_on_scala.html
Scala是一个非常棒的基于JVM语言，JavaEye论坛也有很多文章：
http://www.iteye.com/search?query=scala&sort=&type=topic

如果是你说的这方面那更不应该选择rails了.系统架构,负载均衡...等等现在的java,php来得成熟稳定得多.应该是向快客说的.后期大量功能开发扩展rails会比较便捷

为什么github/lighthouse/twitter要用rails这个破烂？用java/php不是更好？
这种月j话题就没必要讨论了

我完全没有觉得rails不好.只是好奇问问
"Twitter當初為什麽會選型rails呢?Twitter使用不是很多.初步感覺功能頁面也不是很多"
没多少功能的话(可能是我使用不多误解了)还要去处理这么多问题. 好像是得不偿失.但没考虑到后面可能的功能扩展.现在想想也是合理的.如楼上所说是没必要讨论了..

成熟等于一大堆你不需要的feature

稳定等于开始落伍了

好像有点夸张吧～

我倒觉得Twitter当初做的时候并没有想到现在会这么成功，衍生出这么多的需求来。
初了一开始用ruby成本低外，ruby本身的热度也能帮助Twitter快速火起来,成熟起来。
就像豆瓣如果当初不用phython做，测试器的时候基本没人给他抓虫。

我用过Rails做过一些项目，但基本上是正式的商业项目还是考虑用java，毕竟java成熟。
有很多久经考验的类库，一捞一把的开发人员，稳定的社区和大型商业公司支撑等。

Twitter started as a hack project at a company called ODEO, which was focused on podcasting. As ODEO was having some troubles in its latter days as a company, they started experimenting, to keep engineers involved by letting them play around with ideas they had on the side. One of the engineers, Jack Dorsey, had been really interested in status. He was looking at his AIM buddy list, and seeing that all of these guys were saying, “I’m walking the dog,” “I’m working on this,” “I’m going to that.” He wondered if there was some way to make it easier for people to share that status. So he and a couple other engineers started prototyping what became Twitter on Ruby on Rails, which was the stack that ODEO was built on. And Twitter continues today to be primarily a Rails application, with a bunch of Ruby daemons doing asynchronous processing on the backend.
--------
从这段话可以看出，Twitter完全是几个开发人员闲着没事干的产物。

成熟的java很难帮人实现梦想.当然,解决解决就业问题,忽悠忽悠项目,手下管上一帮子民工从而寻找出良好的感觉,那么肯定上java.

我想，是因为用的那个人没有梦想!

不知道有没有朋友确认一下：Twitter上有否用到Erlang？