The results of these "real" GUI designers can be... ahall we say... impressive [jgoodies.com].
Of course, even the "Windows Look & Feel" sample in the example you gave (see this page) does not actually look exactly like what people expect a native Windows app to look like. It is certainly very close, but visibly different. (Although I doubt the differences impact usability at all.)
The is probably the "penalty" for cross-platform compatibility, but it definitely helps advance the argument that Java apps are somehow inferior to native apps, since they can't even get the look and feel right. (I don't agree, but it is certainly arguable.)
Ultimately, poorly written Java apps may have the same general distribution of speed and usability issues that typical (also poorly written) VB or C++ apps have (which I do not actually concede), but since Java apps are visibly distinct (more so even than VB) they will continue to get a bad rap simply because they stand out. Every way that they stand out (in a non-native way) is another nail in the coffin.
Azureus, on the other hand, is a good example of an app that uses slight deviations from typical UI to its' advantage. The configuration UI for Azureus should be an example to other apps (at least, any app with a multi-page configuration), while its' ridiculous memory footprint should not.:) As I said in an earlier post, Azureus does not at first glance appear to be a Java app. It does eventually become apparent, not just due to UI, that it is a Java app after all.
A perfect example of this is the #1 BitTorrent app, Azureus. It looks and works so good that no one questions what is under the hood!
Doesn't this statement disprove your point? The fact that these types of standouts are notable because they are NOT obviously Java means that there is a more general problem that makes them the exception.
Personally, I can usually spot a Java app from a mile away. Although, to be fair, I have not tried the apps you mentioned other than Azureus, which I agree does not appear to be Java-based at first glance.
I'm sure if we'd remove these, we'd end up with something like 3 million, from the number of 5 million posted above. This would mean that SCO would own over 1/3 of the linux kernel code. Yeah.... I beleive that one.
The same ratio of code would be disqualified from whatever SCO is claiming is theirs, as well, so the ratio of SCO to Pure Linux would remain about the same.
Exactly. Using strong-arm tactics to shame people/governments into compliance does not foster a positive world-view of the movement. Why not just pick the right tool for the job? Sometimes this is open source, sometimes not.
Slashdot Mirror
Both of you can suck it.
ignore the "691331" part
Of course, even the "Windows Look & Feel" sample in the example you gave (see this page) does not actually look exactly like what people expect a native Windows app to look like. It is certainly very close, but visibly different. (Although I doubt the differences impact usability at all.)
The is probably the "penalty" for cross-platform compatibility, but it definitely helps advance the argument that Java apps are somehow inferior to native apps, since they can't even get the look and feel right. (I don't agree, but it is certainly arguable.)
Ultimately, poorly written Java apps may have the same general distribution of speed and usability issues that typical (also poorly written) VB or C++ apps have (which I do not actually concede), but since Java apps are visibly distinct (more so even than VB) they will continue to get a bad rap simply because they stand out. Every way that they stand out (in a non-native way) is another nail in the coffin.
Azureus, on the other hand, is a good example of an app that uses slight deviations from typical UI to its' advantage. The configuration UI for Azureus should be an example to other apps (at least, any app with a multi-page configuration), while its' ridiculous memory footprint should not. :) As I said in an earlier post, Azureus does not at first glance appear to be a Java app. It does eventually become apparent, not just due to UI, that it is a Java app after all.
Doesn't this statement disprove your point? The fact that these types of standouts are notable because they are NOT obviously Java means that there is a more general problem that makes them the exception.
Personally, I can usually spot a Java app from a mile away. Although, to be fair, I have not tried the apps you mentioned other than Azureus, which I agree does not appear to be Java-based at first glance.
I would if I had designed the car myself. I would go the extra mile and say you had stolen it, in fact. This is why the analogy works.
The same ratio of code would be disqualified from whatever SCO is claiming is theirs, as well, so the ratio of SCO to Pure Linux would remain about the same.
Exactly. Using strong-arm tactics to shame people/governments into compliance does not foster a positive world-view of the movement. Why not just pick the right tool for the job? Sometimes this is open source, sometimes not.