kmj
09-12-2002, 01:41 PM
Okay,
I'm really interested in seeing some real world comparisons between java and .NET.. For any number of people who say Java's fast enough, there are just as many who say it's too slow.
This is what I'm thinking: we come up with a (few?) apps to benchmark.
A .NET buff writes a version with .NET (any language), and gives detailed instructions on how to install .NET and run the application.
A Java buff does the same with a java1.4 application.
An "independent third party" writes the app in native code, probably C++ or C.
People download the apps, and run them, and reply with their findings... then we try to come together with a consensus.
Now, the main purpose of this is to ensure anyone can see first hand (meaning, running the application) how they compare; not just reading some webpage results. This also means, since the code will be available, that people will be able to check to make sure a programmer isn't doing anything silly to slow down his code unnecessarily.
What is needed:
1) ideas for applications; basically specifications just like for most of the other competitions. In fact, a number of previous competitions would probably work fine as apps.
2) A willing Java Coder
3) A willing NT Coder
4 ) A willing "native" coder
What do you guys thing about this?
I'm really interested in seeing some real world comparisons between java and .NET.. For any number of people who say Java's fast enough, there are just as many who say it's too slow.
This is what I'm thinking: we come up with a (few?) apps to benchmark.
A .NET buff writes a version with .NET (any language), and gives detailed instructions on how to install .NET and run the application.
A Java buff does the same with a java1.4 application.
An "independent third party" writes the app in native code, probably C++ or C.
People download the apps, and run them, and reply with their findings... then we try to come together with a consensus.
Now, the main purpose of this is to ensure anyone can see first hand (meaning, running the application) how they compare; not just reading some webpage results. This also means, since the code will be available, that people will be able to check to make sure a programmer isn't doing anything silly to slow down his code unnecessarily.
What is needed:
1) ideas for applications; basically specifications just like for most of the other competitions. In fact, a number of previous competitions would probably work fine as apps.
2) A willing Java Coder
3) A willing NT Coder
4 ) A willing "native" coder
What do you guys thing about this?