by ewin - 2008-05-15 11:01
Who the fog needs that? It is not as if Sun doesn't have a media API. It is only that the quitters at Sun couldn't be arsed to support the Java Media Framework. It was neglected for years, disowned and left to die a slow painful dead. Sun: Quitters, not finishers.
Developers having invested in it were left high and dry, taken for a ride by Sun, and Sun proved to not be a partner one can trust. Sun doesn't go where it hurts, maintaining their stuff. Instead Sun travels the easy marketing hype road to irrelevance. Sun: Quitters, not finishers.
Now, on its way to irrelevance Sun comes up with some new junk. As if some manager at Sun wants to make a name for himself by showing some initiative. The "Java Media Component API" will die the same slow death as the JMF as soon as said manager got his promotion - or a job at Goggle. Sun: Quitters, not finishers.
Anyone knowing Sun's past "performance" and Sun's utter failure to demonstrate a change in behavior can't recommend the uptake of the Java Media Component API or FX or that other junk you listed. It is DOA. Hey, we are talking about the company that didn't even manage to maintain the JavaComm API for Windows. And the same quitters should now be trusted to maintain another media API? Ha, pull the other one.
So JavaFX is not a "distraction" of resources from the desktop
Of course it is. It distracts from the real desktop issues (which isn't fancy graphics). It takes programming resources away. Resources badly needed for bugfixing. For the life of me I can't figure out how a software development company doesn't manage to fix things like JFileChooser but puts resources on that FX junk. One has to be pretty incompetent to run software development his way.
The same holds for that filthy rich client nonsense. As if that addresses any real-world problems. Ok, it solved two problems. It advanced the careers of these two guys. Good riddance.
by jwenting - 2008-05-15 05:35
As a result people are sticking with what works, 1.4 and to a degree 1.5, while gaining proficiency in things like .NET so they have an exit strategy when the ship finally sinks.
Sun's attitude is loosing them the very people they need most, the experienced professionals, because of their constant hammering to get more inexperienced kids eager to try every new hype to jump onto the bandwagon, kids who will just as readily jump off again when something "new" appears on the horizon, something like Scala, Flex, Silverlight, or whatever.
by erickson - 2008-05-16 12:12
by posttool - 2008-05-15 08:21
by jwenting - 2008-05-14 22:10
by mac_systems - 2008-05-14 04:31
by ewin - 2008-05-14 22:36
Every few years Sun pretends to wake up, proclaims Java's breakthrough on the desktop is imminent, publishes a few marketing papers (from the usual suspects), and then forgets about doing abso-freaking-lutely any improvement. Or deity forgive, any bugfixing.
The history of Java is littered with abandoned or half-done, bug-ridden APIs because at Sun they are quitters, not finishers. FX will be another one.
For now FX gives a clear message. Sun has once again given up competing at the desktop. The previous filth rich client marketing bushwah failed spectacularly (guess why ...), the framework thing didn't take off (guess why ...), so for the moment Sun decided they don't want to push Java for serious desktop applications any more. Instead it has to be something for the web, artsy-hippy people: FX.
But don't worry, after FX's failure, and after a brief stint in the "Enterprise rules the world" phase Sun will come back to the desktop. With yet another half thought through API, never to be going to be finished.
by heliorodrigues - 2008-05-12 13:22
by aberrant - 2008-05-12 11:11
by fabriziogiudici - 2008-05-15 02:44
Nimbus is part of Java 6 Update 10, which is scheduled for Fall. But we have an early access that can be tried, and of course there was a specific session at J1.
For what concerns the "non programmer tool", it has been demonstrated at the keynote an Adobe Photoshop plugin that allows to export graphics into a form directly usable by JavaFX. I believe there has been also a specific session on it, but I couldn't attend it.
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Participation.
Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.