Featured Articles
- Gottfried Leibniz: Shoulders of Giants
- The Art of Noise
- Jeremy Allison gets a name check from Fidel Castro
- That Which Survives
- The twenty-four hour loaf
- Orbiting Debian: Bdale Garbie
- Diving for Perls: The poetry of programming
- Hacking after midnight
- Why should we not tag our politicians?
- Always Crashing
- The Viral Clause
- Tivo, phone home...
- Machine smashing ain't what it used to be
- Requiem for Bell Labs, Unit 1127
- Shakespeare, think tanks, Linux, Atlantis & the AdTI
- Vista - The Tipping Point
- The terminal man & the semantic web
- Benjamin Franklin, Copyright Pirate
- The Executable's Song
- A Free Software Odyssey
- DNA: The Software of Life?
- Let Them Eat Megabytes
- Linux in the Special Effects Industry
- Roll Your Own Hardware
- The land of the Patent Trolls
- Hackers of Ancient Greece
- John Cage and the Copyright on Silence
- Piracy is not all it's cracked up to be
- The Magician of Budapest
- The Revolution will be Plagiarised
- Against Nature - Viral Computing
- Programming as an Aesthetic Experience
- John Clare's enclosure - a tale of copyright law
- Powerpoint: A Pig through the Python


Microsoft standards.
Any programmer that has ever dealt with a Microsoft standard knows what a nightmare it is. They are poorly conceived, poorly documented, and shifting. Something as simple as a CSV file can be an adventure when trying to maintain compatibility with Microsoft products.
Microsoft should just adopt open standards. The time for benefiting from closed standards is past. There are to many options now and they can't be squashed with FUD or by buying them out. People are no longer content to be locked into a little corner - they want to share everything and without jumping through hurdles. As always, the best way to make money is by giving the customer what they want. Don't wage war on the hand that feeds you.