Scripting News

Thu, 19 Feb 2004 15:33:25 GMT

Paul Boutin: "Perhaps Kerry should make a special trip to Harvard to court the Berkman Center's A-list of bloggers for their support." Yes!

Thu, 19 Feb 2004 23:49:52 GMT

We're booting up the Thursday evening meeting at Berkman. We didn't get the new microphone so the webcast is certain to suck. However the IRC channel is probably great.

Thu, 19 Feb 2004 19:00:33 GMT

Chronicle: "Google has become the symbol of competition to the academic library."

Thu, 19 Feb 2004 14:10:24 GMT

Kerry campaign: "We have finished experimenting with the RSS aggregator that was on this page and decided that it did not meet our needs."

Thu, 19 Feb 2004 13:56:05 GMT

Jason Kottke calls Jakob Nielsen an ugly name on his way to making an important point, that the general press doesn't review tech products in a serious way.

Thu, 19 Feb 2004 14:13:07 GMT

News.Com: "Manufacturers plan to start selling notebooks with integrated VoIP this year and plan later to offer notebooks with built-in cell phone capabilities."

Atom use XML-RPC

Thu, 19 Feb 2004 14:36:55 GMT

It's fascinating to read the comments on Russell Beattie's post about the Atom API. His concern is that he won't be able to build a client that talks to a weblog server through his Java toolkit because it doesn't allow the HTTP methods the API calls for. Further, he notes that the spec, which was openly developed, has a restrictive copyright.

The best answer is obvious, imho, use XML-RPC because it already has been adapted to and debugged in all the environments where blogging APIs need to run. By cutting almost to the bottom of the stack you will have to redo everything that took years to do. I think it's going to take longer to redo because XML-RPC didn't need to get any Java toolkits to change, it treaded more softly than the Atom does.

There's a practical side to protocol and format design that's missing in the Atom API. The goal is to make it easy for developers to hop on the bandwagon and get them committed to developing for the platform. Putting unnecessary hurdles in the way unnecessarily limits adoption, and virtually guarantees either stagnation or massive breakage. I can't imagine that either choice is what Google is looking for.

XML-RPC was designed for what they want to do and it's stood the test of time. Learn to love the pragmatic, it's how you're going to win the wars with Yahoo, Microsoft and everyone else who wants to eat your lunch.