Hi > It's not. But the use case is. > While Java is definitely a good approach for business apps, it's unacceptable for edited apps, for which "look and feel" remains a top criteria when the customer makes his choice.
I totally agree on this, even though there is a lot of progress going on. > While Java is definitely a good approach for business apps, it's unacceptable for edited apps, for which "raw performance" remains a top criteria when the customer makes his choice. I do not agree on this any more. Java has prooven to be very efficient and is still improving more and more. Right now, I would say that java applications (if well written) are at least half as fast as c applications (also well written). Suns promotion gives you this: http://research.sun.com/techrep/2002/smli_tr-2002-114.pdf I agree, that Sun has interests on saying that java is fast, but read it. Java is even a lot faster in some areas of computing: Assume, you have code that needs to allocate lots (thousands) of very small objects for a short period of time in memory. In C, where you do not have a garbage collector, you need to free these memory peaces one by one, which is a burdon for memory management and will slow down things. In Java, allocation is fast (just one pointer operation) and there is no need to free things. The garbage collector throws all unreferenced objects of the youngest collection away at once, not processing them one by one. Obviously, in such situations, Java has performance advantages. This seems to be a seldom situation, but it occurs much more often, then you might think. Especially in Java, where every function, that returns more then one value needs to return an temporary object. This seemed to be very costly for me, when I startet using Java, but right now I understood that this is has constant costs - like in no conservative language. Regards, Steffen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
