Alwin wrote this morning a plea for the feuding camps around the RSS/Echo debate to get their acts together and to remember the cost to the user of their antics:
I’m tired of people spending time doing webwork (the web version of wet work) and not coding. I’m pissed off at people trying to assure their place in the spotlight while not taking TLC of the stuff that put them there. Most of all, I’m tired of all the grandstanding and breastbeating.
Isn’t there anybody man (or woman) enough to give a little bit without taking a cheap shot in passing?
I just want all this stuff to work together. Doesn’t anybody get that? Anybody?
I couldn’t agree more. I posted this comment in reply to his post:
Hear, hear. This entire bus load of prima donnas needs a good bitch-slapping. I’m sick to death of the egos and the politics and the posturing. A lot of people I had a lot of respect for have sunk in my esteem in the past couple of weeks.
Okay, so maybe Echo isn’t going to be that tough to implement. There’s still a cost for switching horses mid-stream, no matter how trivial. RSS adoption rates have really ramped up in the past year, much to my delight and benefit. Now, because a bunch of social retards can’t work and play well together, that’s all going to get broken. Even if Echo feeds only take an afternoon to implement, multiply that times the number of people using custom CMS’s and hand-built syndication feeds, plus all of the aggregators and weblogging code that’ll have to be modified, and you’re looking at some serious change that doesn’t have to be spent.
How many news outfits that only just started feeding us RSS or only just upgraded to RSS 2.0 are going to look at this and say “fuck it, all these assholes want to do is bicker and play with new technology, and they have no clue about the costs. Didn’t we get shafted by these guys back in ‘99 already?” and scrap the whole works. Put aside the politics, grow the fuck up, and hammer out a natural, evolutionary means of moving forward from the existing spec.
Do you get it guys? We, the users, are getting tired of this crap. Remember us? We’re you’re customers.
Where’s Doc’s opinion on all this. He’s always ready to jump on the old establishment when they forget who their customers are, but he’s been strangely silent to “call Cluetrain” during the current fracas.
Update: Doc calls bullshit here, in his usual measured, calming manner:
I say was because I’m concerned right now that blogging risks centralization. A year from now, don’t be surprised if everyone with an AOL, an MSN or a .Mac account automatically has a blog, and if those blogs use noncompatible means to interoperate with each other. Just like we’ve seen with instant messaging since the beginning.
And don’t think that other companies with an interest in blogs, such as Google and IBM, won’t find their own ways to defeat interoperation for both competitive and idealistic reasons, no matter how well-intended they may be. They want to make better blogging tools, sell better blogging back-end systems, better ways to put advertising on blogs and better ways to do other stuff. But better isn’t always best. Often (though not always) the better imperative includes protocols, formats and standards that get bettered all the way to isolation and well-rationalized non-interoperability. So, instead of an open market with lots of interop, you got a bunch of isolated silos. It’s not a long trip, and it’s often travelled unconsiously.
Back to blogging. As I understand them, standards like RSS and XML-RPC, as originally conceived, and as still largely implemented, have the virtue of POGE: the Principle of Good Enough. Big-vendor-driven standards like SOAP have a way of going off into non-interoperable directions, based on the compeitive ideals of their participants.
Good stuff. Go read the whole thing.
Updated 7/2/2003 to include Doc’s material.