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.

4 of 480 comments (clear)

  1. J2EE vs. .Net by EggplantMan · · Score: 0, Troll

    J2EE will always lag in performance to .Net technologies due to its interpreted nature. When will you people finally understand this?

    --

    ?-|||-----x<*))))><
  2. Re:Performance isn't most important by MagPulse · · Score: 0, Troll

    Only the fastest Java desktop applications are usable on my PIII 1.2GHz, namely NetBeans and Eclipse, and that's because they don't use Swing. I wrote a Hello World app in C# and it took 2 seconds to start. Language performance will continue to count until we all have 3+ GHz machines.

  3. Lawsuit Time for TMC and their LIES by gavinjolly · · Score: 0, Troll

    The whole review is total CRAP!!! Check out this review of the comparison. It sums up the whole situation pretty well.
    There was no optimisation - it was a stacked deck against J2EE

    --

    The weathers here - Wish you were beautiful

  4. Incompetence rather than malicious act... by GrayArea · · Score: 1, Troll

    I'll go ahead and guess that rather than TMC maliciously rigging the test, the two "experienced" J2EE developers were either incompetent hacks or unprofessional engineers with little pride in their work so it just didn't matter to them. Occam's razor: simplest explanation is most probable...

    It is all the more so stupid of them considering that TheServerSide.com (that also belongs to TMC) would have probably given all the advice they needed if they had asked for it in the first place.

    --
    "The deluded are always filled with absolutes. The rest of us have to live with ambiguity." - Aristoi, Walter Jon Willia