Java Desktop System Review
Reader writes "OSNews has the first in-depth review of Sun's Java Desktop System based on the final code. The article discusses the good (stability, Star Office 7, good Java integration) and the bad (no KDE, buggy RealTek driver, shaky Samba) and it includes a number of screenshots. It seems that Sun has put all its attention on Gnome and while this is good for cosistency across their desktop (some of their Java apps use the native GTK+ themeing), it also limits its users from an out-of-the-box KDE and its thousands of apps choice."
We have seen a lot of articles here in slashdot pointing to OSNews lately, an all of them are by Eugenia Loli-Queru. Am I the only one who hates her reviews? I can't get any substance from any of the writeups.
Life isn't like a box of chocolates. It's more like a jar of jalapenos. What you do today, might burn your ass tomorrow.
That Moz problem she mentioned has bugged me for a long time on every platform: the problem is that real player thinks a file with the extension .rpm is its territory. I wonder if Real will keep claiming "rpm" or give it up?
All's true that is mistrusted
You're looking at it from the wrong perspective. The corporate desktop is not a place to be giving the user thousands of applications from which to choose. Nor even alternate desktops. It's about giving them the tools they need to do the job. Locked down, so the user can't tinker with it and screw things up. Including KDE would have been a terrible choice, no matter which side of the KDE/GNOME divide you fall. Sun need to provice accessiblity. GNOME gives that, and KDE doesn't (yet). So they have to ship GNOME. So their choices are to either ship GNOME or to ship both. For the corporate market, they definitely made the right decision on that score.
"The invisible and the non-existent look very much alike." -- Delos B. McKown
This is from the same reviewer who blamed Fedora Core 1 for her problems compiling a new version of Gaim with the wrong packages installed.
I'd take anything said with a grain of salt.
Cheers Koz
If you want minimal breakage, it just makes sense not to ship (and hence, support) code you don't intend to use. If people want it they can download it...but developers are not the target audience for this product.