Time magazine naming you its Person of the Year intended to acknowledge that user-contributed content has significantly transformed the media business already, and will do so even more in 2007.

User contributed content is not limited to text, as YouTube and other outfits built on rich-media have demonstrated. That trend presents a problem for Java, because Java is especially poor at supporting the creation and interaction with such media types, according to Chris Adamson's recent multi-part blog post, Rebooting Java Media (Act I: Setup and Act II: Development).

Adamson notes that media capabilities today must include not just play-back, but also rich interaction with media:

One of the key concepts of Web 2.0 is “the read/write web”. In other words, if Web 1.0 media was just about watching, Web 2.0 should be about creating, modifying, personalizing, and sharing media. Web 2.0 media is “rip, mix, burn”...

The read/write nature of Web 2.0 requires media libraries to offer creative capabilities and not just playback... Desktop Java needs to offer more ambitious functionality to avoid being rendered irrelevant by webapps, Ajax, and Flash.

The problem, according to Adamson, is that Java almost completely lacks viable means of providing user interaction capabilities for rich-media. An example is the Java Media Framework aimed solely at recording and play-back, but not for editing and otherwise modifying media:

All the abstractions [such as] pointer-like media references, tweens, arrangement of tracks ... don’t exist in JMF. In fact, JMF doesn’t have a useful abstraction of media in a stopped state. To JMF, media is something you play, and optionally “process” (e.g., transcode to another format), and that’s about it. The library offers no deep knowledge of media, and no support for the kinds of tasks needed to create and distribute media.

“Rip, mix, burn” is a great metaphor for what people want to do with their media in the Web 2.0 era. And when Apple says “rip, mix, burn”, what you should hear in the abstract is “capture, edit, export”. JMF’s biggest problem is that it can barely do the first (and pretty much only on Windows), and can’t do the second at all.

While cross-platform, network-ready Java was ideally suited to be the king of rich media on the desktop, Flash, Quicktime, and other technologies eclipsed Java in that niche:

The use of Flash for web media has exploded in the last year or so, oftentimes displacing the classic Real/WindowsMedia/QuickTime troika even for basic playback scenarios. The reasons are easy to understand: Flash has better cross-platform distribution than all of them, and can can offer whatever level of interactivity the developer chooses to provide, from a simple “click button to play” to more sophisticated uses, as in the Schmancy Smashup.

Adamson believes that Java must either catch up with those competing platforms in media-handling capabilities, or desktop Java may be relegated to a small niche:

If Desktop Java doesn’t make a stand here, then frankly, where is it going to assert its relevance? Webapps have eliminated many of the use-cases that applets once targeted, and distribution frustrations (among other factors) continue to make double-clickable Java desktop applications a tough sell. Ajax is all but the final insult: at the end of the day, script manipulating UI widgets in a browser isn’t that different than Java bytecodes manipulating AWT or Swing widgets… except for the fact that Ajax is infinitely more popular than any of the Java client technologies ever were.

To what extent do you expect to incorporate rich-media into your applications in 2007? Do you believe that Java's support for user-created rich-media is important?