Search |
||
We're Gonna Take On The WorldPosted by editor on October 29, 2008 at 7:53 AM PDT
Can the Java Plug-In compete? It's a strange day for Desktop Java developers when AjaxWorld is publishing an article about using Swing for your client-side technology, while the Java sites are asking whether the Java Plug-In is even viable. For the Plug-In story, we'll begin with Marvin Warble's editorial, "Can the Plug-In Compete", which he posted both as a Javalobby editorial and as the beginning of a thread on the java.net forums:
Having walked away from the ever-brittle Ajax market to develop his own Java-based RIA product, Marvin reports that many developers reject it out-of-hand because it depends on the Java plug-in:
So how does the plug-in gain traction? In a follow-up post, he says that a scatter-shot appeal to hobbyists and other amateurs won't make the Java Plug-In viable:
So how about you? What would convince you that you could deploy a business application that depended on the Java Plug-In? Ironically, we're calling attention to this discussion on the same day that our Java Today section also has an article from AjaxWorld (of all places!) about Developing Rich Client Applications Using Swing, in which Mauro Carniel makes the case for Swing (in an applet or as a Web Start-deployed application) as the front end to a multi-tier enterprise application. He lays out the needed data binding and data retrieval tiers needed to connect an enterprise backend to a Swing GUI, and discusses many Swing-based sets of graphic components, including JGoodies, JIDE, OpenSwing, and more. A promised follow-up article will look at IDE support for Swing client-side development. Also in Java Today... Elliotte Rusty Harold thought he new the well-worn The SDN interviews Joshua Bloch about the second edition of Effective Java in More Effective Java With Google's Joshua Bloch. In it, he talks about the folly of premature optimization, writing your own libraries instead of using what's already out there, strange things in Java and undesirable side-effects of signed bytes and of autoboxing, Java's complexity budget, the future of Java, and more. Back in the Forums, Finally, BD-J developer In today's Weblogs, Carla Mott covers GlassFish V3 logging changes. "Logging in GlassFish V3 has undergone some changes to leverage the logging utility in JDK. This blogs reviews where we are with those changes in Prelude and how to use what is there." Masoud Kalali keeps it concise with a One pager review of GlassFish version 3 features. "If you are looking for a simple one page overview of GlassFish version 3 this entry is for you." Finally, Terrence Barr offers an ME perspective on new client-side SE technologies in Java SE 6 update 10 released. "Admittedly, at first sight this has little to do with mobile and embedded Java - but bear with me.Java SE 6 update 10 is big news because it essentially recalibrates the Java runtime and desktop Java." Current and upcoming Java Events :
Registered users can submit event listings for the java.net Events Page using our events submission form. All submissions go through an editorial review before being posted to the site. Archives and Subscriptions: This blog is delivered weekdays as the Java Today RSS feed. Also, once this page is no longer featured as the front page of java.net it will be archived along with other past issues in the java.net Archive. Can the Java Plug-In compete? »
Comments
Comments are listed in date ascending order (oldest first)
Submitted by lafery on Mon, 2008-11-03 15:25.
>What would convince you that you could deploy a business application that depended on the Java Plug-In?
1) The user shouldn't have to know what "plug-in" means and the developer shouldn't have to worry about installing that plug-in on the user's browser. Users are afraid of downloads, pop-ups and security warnings: installs and updates are scary. Helpdesk doesn't want to have to have to worry about yet one more software to support.
2) Nobody cares about becoming a "Java plug-in guru" to find out how to remove the Java logo on startup and other stuff that simply tells the user that something they don't understand is running on their PC.
It seems Sun tries to get users to accept Java plug-in through their developers yet developers are paid by users and can only go where the users want them to go. I think Sun would have more success if it tried to be appealing to the users instead of being more appealing to the developers...
|
||
|
|