An Open Letter:
I woke up this morning three times before 7AM. I was concerned and stressed that RSS is going to die under the weight of techie politics. I'm a natural problem-solver and not a worry-wort, so naturally I began to work on a solution.
The first thing I did was read. I read Mark Pilgrim'spiece over on XML.com's site, written almost 8 months ago, before the political flame war started. It seems reasonable enough and is easy to understand for someone with a basic technical background. I approached the article as a business person and a consultant to business owner. Here's a great format for delivering information on demand using derivatives of a know technology (HTML), but there are 7 different formats controlled by three different groups. Take this information and add it to the recent development of the Echo Project and I can only come to one conclusion: don't invest "real money" yet, wait for the players to shake out.
This is basically the same conclusion that was covered here and here. The words aren't the same, but the underlying theme is: business will shy away from anything that is uncertain. Ask yourself this fundamental question: if you had to invest money to grow your business, do you want to be able to control or predict your costs?
With the current fervor in the RSS/RDF/WTF groups, the average small business owner wouldn't dare take a chance on a technology investment like this. Imagine six months from now having to replace the software and lose communication with customers. That would give the perception that the *business owner* has a problem with *their* server. Who's going to push the compatible client out to all of the users. For free. And help install it. And answer their questions like: "It used to work before, why did it change?" And to be clear, answers like "Dave was a control freak" or "We wanted a better way." isn't going to wash with common computer users. Look at Microsoft's revolving line of OS updates, security patches and new versions of apps. Middle-America doesn't like stuff to change for the sake of change, even if the engineering is flawed, even if the "format needs to be more extensible".
How many times have you heard the phrase "If it ain't broke, don't fix it." Well remember developers, your perception of "broke" is different than that of your users. If your users say it's broken, then fix it. Remember who pays your bills with Kagi/PayPal/AMEX payments for your software.
At the top of this semi-rant, I stated that I'm a natural problem-solver, so in that spirit, if I'm going to complain, I ought to offer a solution. Here it is.
Form a not-for-profit organization as an oversight body. Everyone, and I mean *everyone* gives up their contributions to the oversight body. Then *everyone* works together (no matter how much they hate it/someone/whatever) to come up with something better for the end user.
This is your only viable answer to keep the idea of simple content syndication alive. Business owners like to believe in something that's pioneering but has a measure of structure or control. Linux is a great example. Several daring companies used it early on, but it took RedHat to give more businesses the "excuse" to get it past Finance and Upper Management. The oversight body can accomplish this same thing.
I'm sending this story's permalink to as people as I can in the community, but please, if you are reading this, link it on your site. Leave comments. Speak as users, not developers. Speak as business owners thinking about customers and profits, not politics and personalities.