Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment Re:Java is plainly too slow. (Score 1) 156

I am so sick of people who mindlessly bleat that Java is slow. These people invariably have no idea what they're talking about. I have worked extensively with Swing, Java 2D, Enterprise Java Beans, Servlets, JSP, and more. I have also programmed in C and C++. I also like C and C++ but Java has an awful lot to offer (easy distributed apps with RMI, transaction support with EJB, elegant UI's with Swing, platform independence, a clean language... the list goes on). Please go and download the Java 2D demo and watch real time anti-aliasing, alpha compositing, and bezier curve animations. Please tell me why so many financial and ecommerce companies are building their services on EJB's, when Java is "plainly too slow". There are projects where Java would be less or not appropriate -- device drivers, kernels, daemons.... For the rest, performance is perfectly acceptable, in my extensive experience. The "too slow" argument can be further destroyed by pointing out that you can link and call native code from java, using JNI. So if you have a performance bottleneck -- such as a time-intensive algorithm -- you can write that algorithm natively and call it from java. It is rule of thumb that 90% of a program's execution time takes place in 10% of the code. If absolutely necessary (and normally it isn't), code that 10% natively and let the rest of your application take advantage of Java. On the server side, most of the performance criticism is moot because scalability can be achieved through server clustering. Boxes can be added relatively inexpensively and easily as load increases. Nobody can stop an idiot from writing a slow program in any language. If you know what you're doing, you can write an acceptably fast application in Java.

Slashdot Top Deals

C++ is the best example of second-system effect since OS/360.

Working...