Skip to main content

This Charming Man

Posted by editor on February 25, 2008 at 7:37 AM PST

Of job changes and hypothetical injuries

One of the traits of the online era is that becoming a public figure is something that happens almost by accident. Indeed, it's been said that today's young people more or less expect to have an audience, from their blogs, MySpace and Facebook pages, podcasts, etc. And of course, the standards for how you treat public figures is generally understood to be different from how you treat friends, colleagues, and even complete strangers. In a nutshell, it's expected that public figures are more appropriate targets for criticism and even ridicule. They're famous; they can take it.

Even if they didn't mean to become famous in the first place.

I don't know if blogger Chet Haase minds some of the stuff being said about him. He recently set up a new blog, where he announced he'd left Sun to go to Adobe to work on Flex. This prompted various reactions and interpretations from many quarters, including a online comic by Eric Burke that portrays Chet, holding a bag of money, kicking the personification of Desktop Java in its nether-regions.

Seriously, dude, a little quality control, please?

The idea that Chet was "bought" with a big bag of money is an easy, lazy cynicism that we should all be over at this age. Let's take Chet at his word:

One of the things that attracted me to Flex, and to Adobe, was a client platform that enables very rich user experiences; transitions, animations, filters, and just darned good-looking UIs are all pretty exciting to this graphics geek. I hope to be able to help make Flex an even richer platform going forward.

Burke follows up the reaction to his comic by arguing that key people matter, that Chet's move is bad news for Desktop Java. Maybe so, and maybe it should be a "canary in a coal mine" moment that if Chet says Adobe's platform "enables very rich user experiences", that he's implying Java's doesn't. But even if that's the case, it's not for lack of trying, through some of Chet's efforts like the timing framework project. And if Chet being over at Adobe means that the richness bar is set higher for Java FX, then so be it.

Chet's been a great blogger, author, colleague, and friend; we should wish him well.

John O'Conner considers client-side richness issues in today's Weblogs. In
Java applets not viable for this application?, he writes,
"I've been working with a company that creates a chat system that helps companies sell more of their products online. The backend is all Java, complete with Spring, servlets...all good Java stuff. The frontend is...well, it's Flash."

Roberto Chinnici discusses the divvying up of EE functionality in
Profiles in the Java EE 6 Platform.
"An introduction to profiles in the context of the Java EE 6 platform, and a request for feedback on several Web Profile proposals."

Finally, Onno Kluyt checks in with a report from
FOSDEM 2008.
"Reporting live from the Free Java meetings at FOSDEM 2008. FOSDEM is the yearly weekend gathering at the Free University of Brussels discussing all the F/OSS projects in Europe. Last year we were there for the first time discussing our OpenJDK plans, and this year we are back to look at what we have all achieved over the last year and looking ahead to the coming year."

This week's Spotlight is on the OpenCable Project, announced in a recent press release from the non-profit industry consortium, CableLabs. The OpenCable Platform is a Java-based middleware software layer that "provides the opportunity for operators to deliver interactive services and applications to consumers bundled with their other service offerings. Content Programmers may also leverage the OpenCable Platform to enhance their own programming and advertising offerings and perhaps evolve new businesses around these new services."

In Java Today, the expert group for
JSR 286, Portlet Specification 2.0, has posted a proposed final draft. This next version of the portlet spec "align[s] the Java Portlet Specification with J2EE 1.4, other JSRs relevant for portlet programming, like JSR 188, the next version of Web Services for Remote Portlets (WSRP)." The draft may be downloaded from the JCP page. Final approval balloting is underway now, and ends on March 3.

Over on The Aquarium, Eduardo Pelegri-Llopart points out that You can Vote... on GlassFish Bugs! "I didn't know that CollabNet's Issue Tracker supported votes on bugs.
You will need a Java.Net id, but you can go to your favorite bug
this one,
for example)
and cast your vote(s);
it looks you have a budget of 10 altogether
(I've used
5 of mine so far).
Issue tracker also supports votes in queries:
here are the GF bugs with
>At Least 5 Votes."

The latest edition, issue 159, of the JavaTools Community Newsletter is out, with tool-related news from around the web, welcomes to three new projects in the community (loc-counter, JFugue, and fsmonitor), a Tool Tip on handling paths on Netbeans, and more.

In light of Sun's acquisition of MySQL, there are a number of useful MySQL resources for Java developers available on the Using MySQL With Java page of the MySQL Developer Zone. Essential resources include the MySQL Connector/J JDBC driver, along with its associated documentation and forums. The MySQL Developer Zone also links to tutorials, presentations, and examples of customers using Java with MySQL.

In today's Forums,
whartung points out the power of patterns in
Re: EJB3 Observer pattern.
"As I'm sure you realized, a lot of these patterns are pretty simple to pull off. While we may look to things like the container to already handle these things for us, or something larger like JBI, may times just rolling out something quick and specific to the task is more than enough to get the job done and move forward. The key is simply keeping the abstractions in mind and staying as close to them as practical. Later, even if the underlying technologies change, the abstractions very likely remain the same, so there's little conversion cost later if you do indeed come up with a new need or a better solution in the future."

Bill Foote discusses BD-J performance characteristics and differences in
Re: [BD-J-DEV] BDJ under the hood.
"Implementation techniques are not mandated by the spec, but purely interpreted implementations have all but disappeared. But really, this isn't the right question to ask - equally or more important is processor speed and other aspects of the underlying hardware, like memory bus bandwidth (for graphics blt operations) and classloading speed. Some players are much faster than others; the BD spec does set some recommended minimum performance levels, which helps."

JDIC user candychow complains that he/she
Can't connect to the native embedded browser.
"I have problem when using JDIC 0.9.3 on Linux with Mozilla 1.8a4. I got the following error message: "Can't connect to the native embedded browser. Error Message: Maximum retry number reached!" But sometimes, it works... Can anyone suggest what's wrong with it?"

Current and upcoming Java

Registered users can submit event listings for the href=""> Events Page using our href="">events submission form.
All submissions go through an editorial review before being posted to the

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 it will be
archived along with other past issues in the href=""> Archive.

Of job changes and hypothetical injuries


I totally agree. There is no place for a personal attack on the motives behind Chet's move to Adobe.

I gotta admit that Eric Burke isn't the only one worrying about it. Also, see here:

I didn't mean the comic as a personal's more a statement about the impact to desktop Java.