To view parent comment, click here.
To read all comments associated with this story, please click here.
well, from my point of view, Java, especially the Java 5 is pretty good for server application under heavy load. They are easier to scale too. At least you dont deal with crap load of security or coding issues (buffer owerflows, memory leaks) and it is much faster then scripting alternatives. Tomcat is also doing great if you ask me (5.5.x is particularly good). and note that tomcat is not the only choice.. Resin, Jetty, Orion and of course if you really want App servers they are used in heavy load enterprise sites without a problem.
Read this articles for a change if you want.
Story of wallmart.com's Java-5 transition
http://www.theserverside.com/articles/article.tss?l=MigratingtoJava...
A google engineer and Java talk:
http://java.sun.com/developer/technicalArticles/J2SE/google/limoore...
Become.com, A Massively Scaled Java Technology Application
http://java.sun.com/developer/technicalArticles/WebServices/become/
You see choices, I see security holes, and I already have enough to deal with in the JRE alone, holes that Sun simply sweeps under the rug and ignores, or passes it off as not their problem ("hey, it's not our fault com.sun.blah has a huge gaping hole since jre 1.1") . Pile on sloppy coding, inefficient resource utilization, disregard to users and other developers, fad and buzzword chasing, magic-framework-will-solve-all-problems, overhyped pointless frameworks equivalent to 4 lines of code and you'll see why most devs would rather ditch java as soon as possible. On the other hand, it you're a consultant type, you'll probably love Java the crap creates an invisible dependency on your services; the real hidden cost and vendor lock-in.
Java could benefit from a good kick in the head and massive overhaul.
"A Massively Scaled Java Technology Application" Holy useless buzzwords, Batman! My toilet is connected to a "Massively Scaled Pipe Technology Network". It's also full of shit.
RE: Don't forget Tarantella
People seem to be forgetting than Sun has got pretty impressive cache of technologies for remote delivery of applications over the network/web. Don't forget that Sun bought Tarantella
Which all sounds and works great in theory and marketing-speak, but simply doesn't deliver in practise. These things always miss out critical items which render them unusable and overpriced except for a very small niche. Incidently, their "impressive cache of technologies" happens to be nothing everyone else doesn't already have, or has easy access to.
If there's anything everyone should at least take away from today's announcement if you hadn't got it before, is that Sun is all hype, all marketing, no substance.






Member since:
2005-07-07
I do think like the parent poster, so I'll answer you. Your question is invalid, your description is correct. JRE is stable and robust (well, up to some point that RE should be at least)
What is wrong with Sun's JRE? it is the best available, and very robust. i believe you are just trolling.
With JRE? Nothing. In fact it works vey nice when typical desktop app is being runned on it. If only people would leave Java on desktop and away from heavy load stuff.
With people coding for JRE? A lot. Some people code heavy load server stuff to be runned on JRE. Sloppy memory, heavy load, server? Well, this is a perfect way to oblivion. There are a lot of perfect ways of JRE usage, but whenever I hear Apache Tomcat, etc... I don't want to even think about it (Having such problems once in my life was enough). The only problem is that Java is not a universal tool for all purposes, but some people don't understand that.
And since there is a lot of cases where Java usage is completely wrong (and that is the only reason WHY) there is a lot of people that think like me and many others. As soon as I hear something being done with Java, I step away and don't install. Just too many bad experiences with anything being Java made. Every now and then I try some Java apps, just to see that they aren't any better (less resource hungry).
p.s. Same goes for .Net engine.