1> I had seen a similar post earlier. I went back and found it and it mentioned java2trash (it was posted by you a few days ago), but that post didn't give a URL at that time. http://www.codeproject.com/lounge.asp?msg=374217&kw=java#xx374217xx[^] 3> I'm glad for microsoft for being successful - it's not a bad thing. Sun is a bunch of whiney pricks. Microsoft has strengths no one else can touch. I'm not surprised that Sun has to pursue legal means to level the playing field. Some people have even (stupidly) suggested that if Sun wants to compete, they should create their own OS to compete against Windows and bundle whatever they want with it. (So, apparently, only multi-billion dollar companies that can build their own OS and successfully win the OS wars are allowed to stay in the software business.) I don't use/want java - so this project is a way to get rid of it, as it will shortly be forced down our throats even if we don't want it. Isn't that the same as WMP and IE? I think the only way Microsoft will ever behave itself is by cutting it down to size. Microsoft is abusive because it can get away with it. Now you're working to make them stronger. I think that is *absolutely* the wrong thing to do. Now I get to look forward to even more monopolistic bullying behavior from MS. At least the only people who will use java2trash are Microsoft lovers anyway. ------------------------------------------ "Isn't it funny how people say they'll never grow up to be their parents, then one day they look in the mirror and they're moving aircraft carriers into the Gulf region?" - The Onion

dont even bother with yahoo anymore. digital wasteland springs to mind X|

I wouldn't put it in quite those terms. I found several things interesting: (1) The optimized J2EE performed 10 times better than Suns original setup (which Microsoft did their original benchmarks against). This vindicates Suns assertion that Pet Store was not optimized and was not suitable for benchmarking. Of course, this didn't stop Microsoft from benchmarking it and talking loudly about the results. (Read: Microsoft was more than happy to test against unoptimized applications, despite protests, and then tell everyone it was because of the superiority of .NET) (2) The paper talks a great deal about maximum loads, and .NET does quite a bit better than J2EE in that comparison. But, in terms of pages-per-second J2EE and .NET perform almost identically until you get somewhere into the 1000-4000 concurrent user ranges. (Which makes the idea that J2EE is "a toy" rather insulting to Microsoft - because they can't really outperform it until there are 1000+ concurrent users. Frequently, it requires 3000+ concurrent users before you see much difference.) (3) .NET does do better than J2EE when it comes to cost and number of lines of code. ------------------------------------------ "Isn't it funny how people say they'll never grow up to be their parents, then one day they look in the mirror and they're moving aircraft carriers into the Gulf region?" - The Onion