RDF is DOOMed and other links

• The Future of the World Wide Web, testimony of Sir Timothy Berners-Lee, via Seth Ladd. Some commentry by Nate Anderson.
• Peak Code "At some point, half of the total lines of code for that platform will be written. The further a platform gets past its peak, the less attractive adding new features to it becomes since there is less and less potential return on investment due to the dwindling number of programs that could benefit from the improvements."
• REST Issues, Real and Imagined False Choice: “High” vs. “Low” REST, Red Herring: The Evils of POST, Red Herring: URI Design, Red Herring: Cookies Are Bad and False Choice: Machines vs. People. Sure to be answered in, "REST Books Galore (Sam Ruby also mentions the recent flood of REST books).
• RDFRoom DOOM rendering of FOAF via Semantic Desktop Workshop wrapup
• What engineering has in common with manufacturing and why it matters "Engineering – software engineering in our case – is remarkably like manufacturing, once we shift to view the unvalidated decision as the unit of internal inventory."
• It’s Not RDF versus Microformats "If your world is limited to business cards, social events and reviews then I can see where you might favour expression in HTML. Humans want to read those things too. But the world is bigger than social networking and there are other types of first-class data that people want to exchange with one another."
• Ruby on Rails IDE comparison. Favours NetBeans.
• The State of Swing Mentions one of the small Java 6 enhancements, SwingWorker.

End of SWT vs Swing

EoS ::: Eclipse on Swing "This open source project is named after Eos, the godess of "dawn". If you are familiar with Greek mythology, you probably know why I choose just this name.

Built on SWTSwing, "Eclipse on Swing" is a project to run Eclipse using Swing widgets exclusively."

Complete with Napkin Look and Feel.

Gridbag

IBM Reflexive User Interface Builder "The IBM Reflexive User Interface Builder is an application that constructs and renders graphical user interfaces (GUIs) for Java Swing and Eclipse Standard Widget Toolkit (SWT) based upon a descriptive XML document. (Java Swing is a rich GUI toolkit included with Java that provides operating system-independent GUI components. Eclipse SWT is an add-on GUI toolkit that takes advantage of host operating system GUI components for maximum host integration.) IBM Reflexive User Interface Builder is both a specification for a mark-up language in which to describe GUIs and an engine for creating (and, if desired, rendering) them. This application can be used as a stand-alone application for testing and evaluating basic GUI layout and functionality, or it can be used as a library within the context of a Java application for creating and rendering GUIs for that application."

So you never have to go Totally Gridbag (via Tom).

Combine Two Technologies

Like putting a clock in an existing product I keep thinking of combining an XML Swing library with JSF. It would be nice to use JSF as a way to provide the abstraction for differing rendering technologies (this was the first thing I thought when I saw JSF). This interview had some interesting bits of information on this:
"One of the unique things about Faces is that it allows you to have separate classes for rendering a UI component. So a simple text box can consist of a UIInput component, which represents the concept of collecting user input, and a Text renderer, which knows how to display a textbox in HTML. You can create separate renderers for different types of clients -- one for HTML, one for SVG, and one for WML, for example...the third-party component market will continue to grow, not just with HTML components (which will be first), but also components and renderers that support other devices and richer clients."

"There's a sample in the current Faces early access release of XUL instead of JSP, but I think more work needs to be done to prove that other display technologies can really be first-class citizens."

"JavaServer Faces is also a good technology for thin client applications that aren't HTML-based. I've mentioned WML, but you could also write a Java applet application, or some other non-browser client that works with JSF. We'll see these types of applications evolve over time.

Personally, I think fat clients are great for some applications, like RSS News Readers. But web applications are great for other things, and JSF is a good way to build those types of applications. "

The latest download includes XUL in the non-JSP examples.