MF高度评价DHH和RMH宣称J2EE将死

During the years we worked on Viaweb I read a lot of job descriptions. A new competitor seemed to emerge out of the woodwork every month or so. The first thing I would do, after checking to see if they had a live online demo, was look at their job listings. After a couple years of this I could tell which companies to worry about and which not to. The more of an IT flavor the job descriptions had, the less dangerous the company was. The safest kind were the ones that wanted Oracle experience. You never had to worry about those. You were also safe if they said they wanted C++ or Java developers. If they wanted Perl or Python programmers, that would be a bit frightening-- that's starting to sound like a company where the technical side, at least, is run by real hackers. If I had ever seen a job posting looking for Lisp hackers, I would have been really worried.

Lisp as an Alternative to Java

n a recent study Prechelt (1999) compared
the relative performance of Java and C++ in
Iexecution time and memory usage. Unlike
many benchmark studies, Prechelt compared
multiple implementations of the same task by
multiple programmers in order to control for
the effects of differences in programmer skill.
Prechelt concluded that “as of JDK 1.2, Java
programs are typically much slower than pro-
grams written in C or C++. They also con-
sume much more memory.”
We repeated Prechelt’s study using
Lisp as the implementation language.
Our  results  show  that  Lisp’s  perfor-
mance is comparable to or better than
C++ in execution speed; it also has sig-
nificantly  lower  variability,  which
translates  into  reduced  project  risk.
Furthermore, development time is sig-
nificantly lower and less variable than
either C++ or Java. Memory consump-
tion is comparable to Java. Lisp thus
presents a viable alternative to Java for
dynamic  applications  where  perfor-
mance is important.

然后，后面是如何做实验的。如何出来一堆结果数据。

a {
  b {
    c{
       return from a;
     }
  }
}

(奇怪，这么耸人听闻的标题，竟然没有引来一片哗然。本以为应该有很多java铁杆fans跳出来的。)

Ruby is a great place for other frameworks to fill the gaps left behind by Rails's opinions.

An important point however is that RMH attacked Java EE, not SE

我觉得Robin的标题有误导。RMH的批评主要是针对J2EE平台的。


所以应该说“RMH宣称J2EE将死”。

另外，RMH所说的J2EE平台是否包括spring, webworks, hibernate这些框架呢？还是仅指Sun的J2EE规范呢？

RMH是仅仅指Sun的Java EE 5规范的，不过Spring/Hibernate这些框架的发展方向也在朝着大而全在走。

那是要看它是否想进入更多的领域，要解决的问题越多，自然也就越复杂
rails发展下去估计也会越搞越复杂