Is the Java Plug-In really "annoying"?
A few days ago, ZDNet.co.uk posted an article on applications that tick them off. Annoying software: a rogues' gallery features applications that put themselves in the user's face and run roughshod over their needs. Think Real Player, or the bundled junk-ware that bloats the desktop of a brand-new PC. Or iTunes trying to trick you into switching to Safari. Or think of Java.
Wait, what now? Java?
Yep, Java got dinged by the ZDNet editors on Page 6. They write:
Java doesn't do anything by itself. It's a programming language. Programming languages are like sewage plants: if the average user becomes aware of them, something's gone wrong.
Java doesn't know this. Java wants to be in your face. Java wants to be updated. Java wants to tell you the good news about Sun. Have you heard about Sun? Here's a nice picture of our logo. And fancy a copy of OpenOffice? No? Well, never mind. Java's installed a copy of Yahoo Toolbar in your browser instead. Because that's what programming languages are there to do, right?
I thought this was an interesting hackle to see raised, so I forwarded it on to the Java Posse group for discussion and followup, where several (including JavaFX engineer Josh Marinacci) noted that most of the other offenders were far more annoying. Even the Slashdot followups found comparatively far less fault with Java's presentation.
A discussion about the article is going on in our own forums, and some of the readers agree with ZDNet's original assessment. In
Re: ZDNet gives Java a negative review,
kirillcool (aka, Kirill Grouchnikov) writes,
"Client Java is just way too pushy. I don't see Flex / Silverlight popping any console windows, adding tray icons, or even showing their name in the *default* loading sequence. Why would Java be so adamant in advertising itself with the *end users* is, frankly, beyond my comprehension."
Now, what do you think? Does the Java installer and toolbar plugin enhance the brand or badger the user?
Also in today's Forums,
desibel spells out Swing fundamentals in the followup,
Re: Starting point to understand inside Swing.
"Swing is based on model-view-controller(MVC), so in order to understand swing you have to understand MVC. This is the way Swing controls what to display, how to display it and eventually what will happen to it. All swing components have a GUI and a model + different types of listeners that have to be implemented in order to create an action when something happens in the model or GUI. So basically swing says: don't update the GUI I will update it for you if you update the model. Swing needs an event to be fired in order to do this and in order to create advanced "new" components you have to make and fire that event in the model."
fbratufigures out a configuration problem with GlassFish in
Re: security error when trying to deploy a resource connector.
"That was the problem - I didn't have the security manager enabled!!! I've just found out that Glassfish starts with the security manager disabled by default for a domain created with the developer profile - which is the profile I created in order to test the connector on Glassfish - so I added the -Djava.security.manager option to the JVM, and now it works! Thanks for the help!"
Finally, Shai Almog talks about the state and plans for the Lightweight UI Toolkit in
Re: What are your needs for UI Toolkit ?
"The LWUIT Demo is only a demo. LWUIT itself is early access but is already being used by several vendors for products it is also being used by our team for products. LWUIT will be fully open source under GPL+CE very soon which allows bundling LWUIT in proprietary applications but requires returning changes to LWUIT to the community (no need to open source your application). Swing for mobile devices is AGUI, LWUIT works on top of AGUI when its available. Sun is releasing LWUIT as a tool for the developer arsenal."
In Java Today,
the GlassFish Scripting Project is an umbrella project for projects related to the use of scripting languages in GlassFish. As Jean-Francois Arcand notes, the grizzly-jruby extension is moving out of the Grizzly project to become part of glassfish-scripting. The project also includes resources for discovering supported scripting languages and using them with GlassFish.
A brief interview on Artima looks at the challenge of Testing Multithreaded Java Code. "In this interview from JavaOne 2008, Coverity chief scientist Andy Chou discusses why traditional unit tests don't often help in uncovering concurrency-related errors, and why a combination of static and dynamic analysis yields better results when testing multithreaded code."
In today's Weblogs, Jean-Francois