Lauren Bish
Posts: 1
Nickname: devdude
Registered: Jul, 2008
|
|
Re: Does Anyone Really Care About Desktop Java?
|
Posted: Jul 29, 2008 11:10 AM
|
|
I haven't read the whole thread so excuse me if I repeat anything that has already been stated. I speak as someone who has been writing mostly desktop apps in Swing for almost ten years. None of these were general purpose shrink wrap type apps (like word processors, spreadsheets), but rather vertical market cross-platform apps where *proper* use of Swing excels compared to any other framework (IMO). One doesn't have to look too far to find general purpose Swing apps though - Open Office is one (although it doesn't compare well to MS Office IMO).
I don't think that it is very relevant to compare Swing to Flex - they target two different platforms; Flex targets the web client and Swing targets the desktop. How many desktop apps do you see developed in Flex??
In my experience and opinion there have been a number of reasons Java has not made much progress on the desktop:
1) The footprint of the JVM. This, and the early FUD/branching attempts by MS also helped mortally injure Java in the browser. Sun has been making progress lately with trimming down the VM, but it is still much larger and much less ubiquitous than Flash/Flex or JavaScript.
2) A lot of consumers (and even some security "experts") confuse JavaScript with Java, then they hear about the dangers of JavaScript and don't want Java installed on their computers. I am still encountering this, even from IT departments that should know better.
3) Swing developers themselves have hurt Java on the desktop. The devs used non-standard look & feels because they could, not because they should (it is rare that you need to use a non-standard L&F), and Sun didn't help in this regard by promoting these look & feels. Many of the Swing apps I have seen, such as Open Office and even the latest version of Netbeans have a clunky feel and some outright bugs in the UI. This is not a problem with Swing or Java, but rather the incompetence and sloppiness of the developers. As already mentioned, a lot of users see this and associate it with Java/Swing instead of with the developers.
Sun has done some improvements with the native look & feels, and needs to do some more. Sun also needs to stress to developers to use the native L&Fs unless there is a compelling reason not to - I don't see that happening anytime soon.
The clunkiness and design of Swing is very low on my list of problems with Java on the desktop. Swing is not perfect, and neither is Java, but I much prefer both to the alternatives.
I'll probably think of some other issues, but the big one right now is that many apps are going online as web client apps. Swing applets inside of the browser are usually not the answer for many of these apps, although for some proper use of Swing in an applet might the right answer. The early improper use of applets in web sites also hurt Swing/Java.
I am using GWT and not Flex for web clients for a number of reasons:
a) I can develop in one language on both client and server. This means my experience and knowledge transfer ratio from Swing and Java is high. I can also handle localization and accessibility issues in a better fashion. GWT is very similar to Swing in many respects.
b) No plugin required.
c) Very efficient (in both size and performance) and more ubiquitous than Flash/Flex. Open source and cross platform.
|
|