Linked by Thom Holwerda on Sat 8th Oct 2005 18:40 UTC, submitted by anonymous
Permalink for comment 42079
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/20/13 6:17 UTC, submitted by MOS6510
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
More News »
Sponsored Links



Member since:
2005-10-08
"Concur. While Gosling is orders of magnitude smarter than me, when I saw JBoss take longer to boot than the Lose2000 OS on which it ran (the app in question was rather minimal), something ~3 minutes, IIRC, I thought: wow, no need to shop for a turkey this Thanksgiving..."
Speed of startup on a Web application server is of little importance. Performance when it is running is what matters. And when it comes to performance of Web applications written in Java, typical algorithms benchmark 10 to 15 times faster in Java than in Perl. (Java compiles mathematical algorithms that are commonly used down to native code with Hotspot). So Java would seem to be a much better option for a complex Web app than Perl for example. And for obvious reasons, C / C++ are usually not good options for writing Web applications.