[Valid RSS] This is a valid RSS feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="utf-8"?>
  6. <rss version="2.0">
  7.    <channel>
  8.        <title>The Wannabe Java Rockstar</title>
  9.        <link></link>
  10.        <description>The Wannabe Java Rockstar: Janek's weblog where all posts go to Eleven</description>
  11.        <copyright>(c) 2004, 2005 Janek Schwarz</copyright>
  12.        <generator>Fog Creek CityDesk 2.0</generator>
  14.        <lastBuildDate>Fri, 18 May 2018 21:15:00 +0100</lastBuildDate>
  15.        <managingEditor>[email protected]</managingEditor>
  16.        <webMaster>[email protected]</webMaster>
  17.        <language>en-us</language>
  20.    <item>
  21.    <title>The state of client-side Java HTML rendering</title>
  22.    <category>Java</category>
  23. <description><![CDATA[<p>I don't know if this thing is still read by people. In any case, I need a solution for HTML rendering in Java desktop application. Currently, my application uses <a href="">NetClue</a>, but the company seems to be defunct. Well, NetClue has always been a bit flaky when it comes to in-the-wild-HTML, but it wasn't that much of a problem as we control the HTML generation.</p>
  24. <p>But now the application needs to consume "third-party generated" HTML code too. And NetClue tends to stall the whole application when it encounters HTML it doesn't like.</p>
  25. <p>So I'm looking for alternatives, pure Java ones preferred. What HTML renderes are available and what are the licensing options?</p>]]></description>
  26. <link></link>
  27. <guid></guid>
  29.    <pubDate>Wed, 02 Aug 2006 23:07:58 +0100</pubDate>
  32.    <comments>;commentid=060802230758</comments>
  36.  </item>
  38.    <item>
  39.    <title>What were they thinking?</title>
  40.    <category>Technology</category>
  41. <description><![CDATA[<p>Last week I had the joy of setting up email using <a href="">Exim</a>&nbsp;on a new <a href="">Debian</a> box. Usually you find the configuration in <tt>/etc/exim4/exim4.conf</tt> or a similar location. But Debian does it differently. To quote the Exim <a href="">faqs</a>:</p>
  42. <blockquote><p>The Debian Exim 4 package uses a quite uncommon, but elegant, method of configuration where the “real” Exim configuration file is assembled from a tree of snippets by a script invoked just before the daemon is started.</p></blockquote>
  43. <p>Stuff like that makes me sick. Why on Earth can't they do it as everybody does? Screw elegance, I want it easy. Not only does it Debian differently, they also chose to document it poorly. Eventually, you'll find everything in <tt>/usr/share/doc/exim4/README.Debian.gz</tt>, but this file is a disorganized pile of I-don't-know-what. I wasted 4 hours with this crap.</p>
  44. <p>All I wanted was having emails delivered.</p>]]></description>
  45. <link></link>
  46. <guid></guid>
  48.    <pubDate>Sun, 29 Jan 2006 09:15:29 +0100</pubDate>
  51.    <comments>;commentid=060129091529</comments>
  55.  </item>
  57.    <item>
  58.    <title>DOCX vs. DOC or: Proprietary XML Formats vs. Proprietary Binary Formats</title>
  59.    <category>Technology</category>
  60. <description><![CDATA[<p>In the <a href=";commentid=051020224038">comments</a>&nbsp;to my last <a href="Archive/2005/10/20/AbouttheUselessnessofOpen.html">post</a>, Charles asked why a proprietary XML format was better than a proprietary binary format. Well, my point wasn't that it is; my point was that OpenDocument isn't useless, which Dave Winer claimed it is.</p>
  61. <p>But: I prefer the XML based Office 12 formats to the old DOC/XLS/PPT formats. Even if they are still proprietary. Here is why:</p>
  62. <ul>
  63. <li>Microsoft <a href="">specifies</a> the new formats and puts the specification under a <a href="">royalty free license</a> (whatever that means). I think this is a huge improvement over the old formats, which weren't specified at all. There has to be a reason it took the developers years in order to implement decent import/export filters for DOC. (BTW, isn't it ironic that the XML Formats Guide is only available as DOC file?)
  64. </li>
  65. <li>The new format is processable by everyone. ZIP tools and XML parsers are available for almost every programming language on almost any operating system. For the first time, everybody can work with Office documents without having to depend on third-party tools.
  66. </li>
  67. <li>Considering the points above, it will be much easier to integrate with Office. At my company, we develop a Java-based business application. Export to Office applications is a much requested feature. We can only go so far with the current CSV based export to Microsoft Excel.
  68. </li>
  69. </ul>
  70. <p>That said, I still prefer OpenDocument, but I also have to consider the market realities.</p>]]></description>
  71. <link></link>
  72. <guid></guid>
  74.    <pubDate>Sat, 22 Oct 2005 22:51:55 +0100</pubDate>
  77.    <comments>;commentid=051022225155</comments>
  81.  </item>
  83.    <item>
  84.    <title>About the Uselessness of OpenDocument</title>
  85.    <category>Technology</category>
  86. <description><![CDATA[<p>OpenDocument is a waste of time and money. At least if you believe Dave Winer, who&nbsp;<a href="">wrote</a> about Microsoft's new XML-based file format for Word:</p>
  87. <blockquote><p>One would think that [the new format] would spawn an explosion of new products designed to please Office users but that's not what's happening. A group of large technology companies is proposing a competing set of formats, and has formed an alliance to confuse the market, and at least double the work of any developer who might want to support their products (with almost no installed base) alongside Microsoft's (with a monopolistic dominant installed base).</p></blockquote>
  88. <p>Unfortunately, Dave got the facts wrong. According to <a href="">Wikipedia</a>, the standardization of OpenDocument at <a href="">OASIS</a> started in 2002. It was decided to build on an earlier version of the format, which was already in XML and had been in use since 2000.</p>
  89. <p>At this time, nobody at Microsoft talked about the XMLification of the DOC format. So one could argue that's file format together with the standardization process at OASIS actually forced Microsoft to develop the XML-based file format we'll see in Office 12.</p>
  90. <p>Who knows, maybe that's OpenDocument's only success. In any case, it is not a waste of time or money.</p>]]></description>
  91. <link></link>
  92. <guid></guid>
  94.    <pubDate>Thu, 20 Oct 2005 22:40:38 +0100</pubDate>
  97.    <comments>;commentid=051020224038</comments>
  101.  </item>
  103.    <item>
  104.    <title>What's up with hard drives these days?</title>
  105.    <category>Technology</category>
  106. <description><![CDATA[<p>A little bit more than a year ago, my hard drive died. It was a rather <a href="Archive/2004/09/10/BackFromTheDeath.html">unpleasant experience</a>, I lost a lot of important data. I bought a new drive, set up the computer again, and went on with life. Five days ago, this drive died as well. I had current backups so it wasn't a disaster, but I can't help but wonder about the quality of drives manufactured by IBM and Hitachi.</p>
  107. <p>I decided to dump IBM/Hitachi -- the new drive is the <a href=";nav=ISH_PRS&amp;frame=content&amp;model=MK8032GAX">MK8032GAX</a> from Toshiba. My only hope is that it lasts longer than the old one.</p>]]></description>
  108. <link></link>
  109. <guid></guid>
  111.    <pubDate>Wed, 19 Oct 2005 20:51:28 +0100</pubDate>
  114.    <comments>;commentid=051019205128</comments>
  118.  </item>
  120.    <item>
  121.    <title>History Repeating</title>
  122.    <category>Music</category>
  123. <description><![CDATA[<p>It's said that history doesn't repeat itself.&nbsp;&nbsp;Back in 1997 I went to a show that I consider to be the best rock show I've ever been to: <a href="">Social Distortion</a> played Berlin's <a href="">SO36</a> supported by the then young and unknown <a href="">Backyard Babies</a>.&nbsp; Unfortunately, Social D haven't been to Europe since then, so that show was the first and last time I've seen them live.</p>
  124. <p>This will change! Tonight, Social D play Berlin, again supported by the Backyard Babies.</p>
  125. <p>We sold the kids to the grandparents and plan to have a great night. I dearly hope that this time history repeats itself -- hopefully neither as tragedy nor farce.</p>]]></description>
  126. <link></link>
  127. <guid></guid>
  129.    <pubDate>Sat, 13 Aug 2005 22:50:33 +0100</pubDate>
  132.    <comments>;commentid=050813225033</comments>
  136.  </item>
  138.    <item>
  139.    <title>Kitikat: Why Should I Use It?</title>
  140.    <category>Java</category>
  141. <description><![CDATA[<p>I found the <a href="">Kitikat framework</a> via <a href="">Erik's linkblog</a>. "Funny name, let's check It out" I thought. The problem is: I studied the whole web site and I still don't know what this thing is about. It states</p>
  142. <blockquote><p>The Kitikat Java Framework is a powerful but simple Datastore processing framework.</p>
  143. <p>A Datastore represents an in-memory copy of data. A program may retrieve the data from a data source, such as a relational database, manipulate the data and then propagate the updates of the data back to the original data source or to a different data source. Once the data is retrieved, it is a disconnected, data source independent version of the data. A change history of the data is maintained to provide dynamic updates to a data source and there are several levels of concurrency control provided for multi-user environments.</p>
  144. </blockquote>
  145. <p>It goes on with a list of features, supported application servers and a quick start guide.</p>
  146. <p>The most important thing this web sites lacks is the answers to questions such as</p>
  147. <ul>
  148. <li>Why should I want to use this software?
  149. </li>
  150. <li>What kind of problems does it help me solve?
  151. </li>
  152. <li>Why is it better than product X, Y and Z?
  153. </li>
  154. </ul>
  155. <p>I'm pretty sure the developers of Kitikat know the answers. They must have thought of typical use cases and applications. It's a shame that the web site doesn't communicate it.</p>
  156. <p>I don't want to pick specifically on the Kitikat guys. It's just that I read the blurb on the front page, scanned the documentation and went "Huh?". I'd really like to know what I could do with it.</p>]]></description>
  157. <link></link>
  158. <guid></guid>
  160.    <pubDate>Wed, 10 Aug 2005 21:25:09 +0100</pubDate>
  163.    <comments>;commentid=050810212509</comments>
  167.  </item>
  169.    <item>
  170.    <title>Green Day Takes Early Records From Lookout Records</title>
  171.    <category>Music</category>
  172. <description><![CDATA[<p>Wow, this is <a href="">big news</a> in punk rock land: Green Day pull their early two records from Lookout Records. In response, the label lays off 6 of it's nine employees. <a href="">Lookout</a> used to be a huge independent label and was responsible for the pop punk explosion in the mid-Nineties.</p>
  173. <p>Apparently, Lookout hasn't been paying Green Day for ages. Given the fact that the early Green Day records were Lookout's cash cows, this is incredibly stupid. Of all artists on Lookout's rooster, Green Day should have been the ones who always receive payments on time. But they did not. After years of not being paid, it seems that Green Day felt they had to do something about it.</p>
  174. <p>This is not about money. In an interview with Green Day, I read that their major label debut <em>Dookie</em> &nbsp;sold more than 30 million units. These guys are multi millionaires, they don't need the money.&nbsp;&nbsp;In fact, according to MTV, Green Day did not file legal actions against Lookout to recoup the payments. They only took control of the CD masters.</p>
  175. <p>One can only wonder what the management of Lookout was thinking. You can't run a business by not paying artists and using the money for funding the operation and new releases that nobody buys. The label published an <a href="">open letter</a>, but it still leaves me with questions.</p>
  176. <p>What really makes me mad is this: Lookout is the home of <a href="">MTX</a>, one of my favorite bands. I guess the plans to release a new CD together with a greatest hits record in 2006&nbsp;&nbsp;just got scrapped. Damn.</p>]]></description>
  177. <link></link>
  178. <guid></guid>
  180.    <pubDate>Sat, 06 Aug 2005 14:10:54 +0100</pubDate>
  183.    <comments>;commentid=050806141054</comments>
  187.  </item>
  189.    <item>
  190.    <title>The History of Ant</title>
  191.    <category>Java</category>
  192. <description><![CDATA[<p><a href="">Conor</a>&nbsp;gives a fascinating <a href="">summary</a> of the development of Ant. I found the bits about Ant2 particularly interesting. Devoted followers of ant-dev might already know that several efforts competed to become Ant2. All of them have died.</p>
  193. <p>Instead, the developers decided to evolutionary improve Ant 1.x.</p>
  194. <p>Good read.</p>]]></description>
  195. <link></link>
  196. <guid></guid>
  198.    <pubDate>Fri, 05 Aug 2005 00:11:20 +0100</pubDate>
  201.    <comments>;commentid=050805001120</comments>
  205.  </item>
  207.    <item>
  208.    <title>The Best Way to Add a Context Menu to Text Components</title>
  209.    <category>Java</category>
  210. <description><![CDATA[<p>There's an excellent <a href="">discussion</a> over at Javalobby on how to add context menus to text components in Swing. In Windows, textfields have a context menu with entries suchs as cut, copy, and paste,&nbsp;&nbsp;which is not available in Swing's Windows look and feel.</p>
  211. <p>Surprisingly enough, the discussion is pretty civilised and lacks the typical "Sun will never get native fidelity right" and "Stuff like that makes my Swing application look unprofessional" posts.</p>]]></description>
  212. <link></link>
  213. <guid></guid>
  215.    <pubDate>Fri, 29 Jul 2005 23:44:06 +0100</pubDate>
  218.    <comments>;commentid=050729234406</comments>
  222.  </item>
  225.    </channel>
  226. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda