Replies

It's the hottest thing in corporate IT, but it needs a high-speed connection to really come into it's own. So consumers won't see what we're using in corps until high-speed internet access penetrates the market.

Sorry, I forgot to make a comment on this one in my last post.

Saying that it just needs faster machines to work properly isn't what I'd call a selling point. The point is, similar apps written in C++ will run more quickly on current machines with current connection speeds then will Java. Hell, even ones written in VB will.

From what I understand, a large part of the problem stems from the fact that Java is an interpreted language and not a compiled one. If it were, it'd be faster and we wouldn't be arguing over Java's relative merits.

From what I understand, a large part of the problem stems from the fact that Java is an interpreted language and not a compiled one.

You're mistaken. For 90% of all programming tasks, Java runs just as fast as C++.

Java 'Just In Time' VMs actually compile the Java code into native binaries and then execute them. There is no difference in how they execute. The *only* difference is that Java isn't set up to handle serious number crunching and massive amounts of I/O, because we've found that 90% of all software doesn't need to calculate more than 1,000,000 times a second.

You clearly are going on what you were told about Java, and have not looked at it, I'm afraid.

I think *that* may be why you get so much push back on your Java criticism. If you're just uninformed . . .