Slashdot Mirror
Another J2EE vs .NET Performance Comparison
Starting yesterday, we received a bunch of story submissions about a
performance comparison between J2EE and .Net. It didn't seem all that exciting, and we sort of ignored the story. But as usual, it appears that some people take issue with the methodology and conclusions.
Aaeennnnnggghhhh, sorry, wrong answer, thanks for playing.
.NET.
...
The report states the exact opposite, 14,004 for J2EE, 2,096
The linked rebuttal raises some valid questions about the accuracy and importance of that stat, so take it for what it's worth
That's funny... that's the polar opposite of this graph.
Bah, but who really cares? Hell, I actually own a pet store, and I use neither of these. A simple off-the-shelf system works great for me, and speed isn't an issue. I don't give a rat's ass what it's written with, as long as it works. Just like I don't care whether the parts in my stereo came from China or Taiwan, as long as it works.
Actually, that article is wrong. If you look at the original test document linked up above, you'll see that the Register actually got it backwards.
.NET Pet Shop 2.0 implementation, Microsoft has done some further optimizations to reduce its overall line count, while also extending the application with new features for distributed transactions and Web Services. The new .NET Pet Shop 2.0 contains a total of 2,096 lines of C# code (the 1.5 version had a total of 3,484 lines of code, a 40% reduction)."
From the pdf above (emphasis mine):
"The Middleware Java Pet Store 2.0 implementation uses the same basic EJB-recommended architecture as the original Java Pet Store (except fully optimized for performance). Hence, its code count remains largely unchanged over the original at 14,004 lines of total code.
With the
Take it for what you will.
Qualitas edurus commercium, nullus penitus net rimor, nullus deus beneficium