|
Thanks for listing some other Sun junk. Take the mentioned "Java Media Component API", for example.
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. |
java.net RSS Feeds
