Slashdot Mirror

Why Java Will Always Be Slower than C++

You drooling java fanboys are all alike. Doing a google search on "java" doesn't prove anything about Java's performance (seriously- those werent even benchmarks you linked to). Neither does linking to a page titled "C++ Sucks".

Here is some data right back at you:
http://www.jelovic.com/articles/why_java_is_slow.h tm
http://dir.salon.com/tech/col/garf/2001/01/08/bad_ java/index.html
http://www.advogato.org/article/624.html
http://www.cs.colostate.edu/~cs154/PerfComp/

Chew on dat, butt monkey.

JAVA is the developers' programming language.

With all respect, that's crap. Java is the _managers'_ programming language of choice. It enforces a particular style of programming (right down to naming convontions), it takes a specific programming 'paradigm' (OO) to an unnecessary extreme and it's chock full of trendy buzzwords and BiCapitalised MumboJumbo. Perfect for PHBs.

JAVA may be slightly slower than other languages,

Says the Iraqi Information Minister.The fact is that, thanks to it's use of garbage collection and because it stores non-primitives on the heap, Java will always be _significantly_ slower than C/C++, no matter whose JIT you are using.

This article explains it well.

One thing to remember is that Java is a 'marketed' language. Hence, be aware of inevitable corporate propaganda. That's not to say that Java is bad, but it is heavily pushed.

Here's a bit of an antidote: Why Java will always be slower than C++

I've coded some of the largest and most functional applets I have ever seen for FutureSource. Here's an example.

During the few years that I have worked in Java, MS JVM was hands-down the best platform. It was fastest, had least bugs, and absolutely compatible with the code I initially wrote Sun's JVM.

Sun's JVM has a bunch of bugs that Sun is refusing to repair for years. For example, the clipping region of Graphics obtained through getGraphics() in Swing is wrong and has been wrong for N years.

Netscape had a terrible Symantec JVM. Working with it was a nightmare.

Microsoft's JVM certainly had its quirks, but much less than the other two.

Dejan

Most programmers are much better at pumping briskly with their right hand.

Dejan

Oh and here is Why Java will always be slower than C++

The thing that bothers me about Mondrian is that it uses only boxed data types, which are all allocated on the heap. That's gonna hurt the performance badly.

I once tested Java's int vs. class Integer for some matrix calculations. Calculations using the class Integer was 16 times (!) slower.

Dejan

When I first tried Eclipse, I was very impressed.

First of all, it looks good. Much better than any other Java program I tried.

Second, it used a single main window instead of multiple floating ones. Us stupid Windows programmers find multiple floating windows visually confusing. There is nothing worse than seeing one's desktop bitmap with all those shiny icons in betweens one's editor and one's toolbar. (Even MDI is dying out as a concept and being replaced with a single window with tabs representing open files at the top. The only people still prefering MDI are traders, because they generally set their workspaces up to view as much info as possible and then just monitor them.)

Third, it's the first well-made piece of software I've ever seen from IBM. IBM has a history of producing inferior software on the PC platform. I once heard someone from IBM refer to his colleagues as "ninjas". If they spent more time working on their programs and less time dressed in black pajamas throwing metal stars, maybe their code would be better.

Fourth, the plug-in concept is well executed. Usually abstraction and usability don't go well hand in hand, but using Eclipse was just as comfortable as using JBuilder which is a Java-only IDE.

So why an I not using Eclipse? Because their Java plug-in is still not robust enough.

I had a rather large project that I was working on. It worked fine in JBuilder and JDK with Ant. But when I loaded those same files into Eclipse, simply touching some of them caused Eclipse to puke.

Must have been some programming construct I used. But if a tool doesn't offer a simple migration path, most people are not going to switch. More to that point: Why can't Eclipse import JBuilder and Forte project files? That would also ease the transition.

Dejan
www.jelovic.com

If you found the text from the original post funny you might want to check out the Career Guide for Engineers and Computer Scientists by Philip Greenspun.

Dejan
www.jelovic.com

What are the radiation levels of 802.11a and 802.11b compared to common household appliances?

I use my laptop 10 hours per day and I'm not sure I want my brain bombarded with energy all that time.

Dejan
www.jelovic.com