The Java Look-and-Feel Debate
Linked by Andy Roberts on Thu 19th May 2005 19:33 UTC
Java Java Swing comes with "pluggable look-and-feel technology", which essentially boils down to the fact that interfaces can be "skinned" (although this is simplifying a tad) and is therefore, extremely flexible. By default, Java ships with a cross-platform look-and-feel (LAF), which means your apps can look consistent across all platforms, or LAFs that mimic the look of a specific platform, say Windows, for example. However, one of the chief complaints of Java desktop applications is its "look". It basically stems from two issues:
E-mail Print r 0   · Read More · 89 Comment(s) http://osne.ws/87d
Permalink for comment
To read all comments associated with this story, please click here.
@deepspace
by Archangel on Fri 20th May 2005 23:11 UTC

Who cares about startup? If I run a programme all day long, I can wait that extra second.
Yeah that's fine, but you were talking about Java not being slow. I am pointing out that it in fact is slower than many other languages, notably C/C++.
Maybe you don't care about it being slower, but that doesn't mean it's not.

That's true. C doesn't do anything... What's efficient about that?
If you'd read what I posted, I explained why.
If you try to access element i of an array, Java will check if that's okay or if it's out of bounds, even if you know it's not. That is inefficient, and is slower than a language that doesn't check it.

Anyway, it seems you're now trying to change your argument to being something about development times, which fully isn't what you said in your original post. I won't argue that Java's going to be developed faster, but that is NOT what you said - you were talking about application speeds.

Looks like mattb's jumped in with some similar stuff. Best note that in fact Java DOES compile as it goes; I know what javac is and what it does, ie it only does half the job. The bytecode still has to be turned into commands that can be executed.