Bill Kearney responds
5th April 2003
Sure, the trouble is getting the developers of the applications creating the RSS to stop being pigheaded. This is, unfortunately, a non-trivial matter. Several battles have been waged, to varying degrees of success. Fundamentally, there’s a faction that naively worries about ’readability’ of the XML. Then there’s a crowd that worries about the verbosity. Over in another corner is the ’but I want to theoretically be able to use mod_kitchensink in my RSS’. Meanwhile, vendor jockeying with proprietary, half-baked extensions keeps happening, over and over...
The fortunate thing is diversity. As more tools come online it becomes apparent that giving the users what they want often means switching tools. When one tool doesn’t cut it, the users switch. Witness the incredible growth of MovableType. It defaults to creating RSS-1.0 files and makes a lot of use of RDF (via trackbacks). The users never see the gritty details, they just see nice functionality and use it.
The other comments are well worth reading as well.
More recent articles
- Datasette Enrichments: a new plugin framework for augmenting your data - 1st December 2023
- llamafile is the new best way to run a LLM on your own computer - 29th November 2023
- Prompt injection explained, November 2023 edition - 27th November 2023
- I'm on the Newsroom Robots podcast, with thoughts on the OpenAI board - 25th November 2023
- Weeknotes: DevDay, GitHub Universe, OpenAI chaos - 22nd November 2023
- Deciphering clues in a news article to understand how it was reported - 22nd November 2023
- Exploring GPTs: ChatGPT in a trench coat? - 15th November 2023
- Financial sustainability for open source projects at GitHub Universe - 10th November 2023
- ospeak: a CLI tool for speaking text in the terminal via OpenAI - 7th November 2023
- DALL-E 3, GPT4All, PMTiles, sqlite-migrate, datasette-edit-schema - 30th October 2023