Linked by Thom Holwerda on Thu 21st Oct 2010 09:13 UTC
Mac OS X After the news that the new MacBook Airs do not ship with Flash pre-installed (which is news considering Flash has been part of Mac OS X for a very long time), we now have news that Apple is also taking what appears to be the first steps towards removing Apple's own Java runtime from Mac OS X.
Thread beginning with comment 446231
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Would be a way to enforce ...
by tetek on Thu 21st Oct 2010 09:45 UTC in reply to "Would be a way to enforce ..."
tetek
Member since:
2010-10-04

This "write once, run everywhere" in terms of GUI is overestimated. Apps don't feel native. And as a user of mac I don't see many java apps those days. Not the good one anyway. If it isn't used - it probably will be removed. Like from windows.

Reply Parent Score: 5

native GUI
by pica on Thu 21st Oct 2010 09:58 in reply to "RE: Would be a way to enforce ..."
pica Member since:
2005-07-10

last time I tested a Java Application on OS X -- if I remember correctly it was 10.1 -- the Java default Metal look & feel was the only option. Well, I admit, to me it looked somehow strange on the OS X desktop ;-)

But the actual Windows and GTK+ (Gnome) look&feel options -- to me -- look and feel native.

pica

Reply Parent Score: 2

RE: native GUI
by kaiwai on Thu 21st Oct 2010 10:04 in reply to "native GUI"
kaiwai Member since:
2005-07-06

last time I tested a Java Application on OS X -- if I remember correctly it was 10.1 -- the Java default Metal look & feel was the only option. Well, I admit, to me it looked somehow strange on the OS X desktop ;-)

But the actual Windows and GTK+ (Gnome) look&feel options -- to me -- look and feel native.

pica


Take JEdit as one example - all the short cuts are set to ctrl instead of command on the Apple Mac; that is one example of why multiplatform applications using Java royally suck. There are numerous other examples, Netbeans, Limewire, Eclipse etc. There is always some quirk that makes it stand out like a sore thumb because at the end of the day if you try to be everything to everyone then you'll fail to satisfying anyone.

Reply Parent Score: 6

TheGZeus Member since:
2010-05-19

I should be the one to decide whether or not that matters to me.
Also, no one uses Swing any more, unless they're using Clojure.
Most people use the native toolkit for any given platform.
I'm no fan of the JRE's memory usage, nor of the Java language (though the bytecode spec is actually a reasonable Forth), but saying "well, it doesn't matter if they don't let you use it, because it sucks anyway" doesn't change the fact that this is anti-choice.

Reply Parent Score: 1

Bill Shooter of Bul Member since:
2006-07-14

Your comment is very frustrating. The reason why I bought my JObs forsaken macbook, was because of the Java and python bindings for coacoa. You could write programs in either of those languages and get a native Mac look and feel. But, Apple ... just ... stopped ... upgrading those. So they really just suck now. They made some great promises about Java being a First class language, and they just let it die a slow death. Apple is a very frustrating company to depend on.

I suggest doing so, only if one has a high tolerance for hypocrisy and insanity. What is promised tomorrow may be forgotten today.

Reply Parent Score: 6

TheGZeus Member since:
2010-05-19

What is promised tomorrow may be forgotten today.

Took me a second.
"Wait, wha- ...oh."
I'll have to remember that one, as I love getting that reaction out of people.

Reply Parent Score: 1

nemith Member since:
2005-07-28

Actually the native look has been a part of Java for some time now. Gone are the ugly Motif style windows in OS X and Windows. Java easily does native style.

Reply Parent Score: 1