Missing the point
16th June 2003
The Register’s coverage of the end of development for IE on the Mac makes some worrying conclusions:
Had Apple worked with inspired vigor since January to improve Safari, users might feel safe without IE. This hasn’t happened. Plenty of improvements have been made, but Safari still lacks the widespread Web site compatibility needed to be the sole browser of choice.
In addition, the horrid state of IE makes life without it seem a rather pleasant concept. Who needs a rectangle with no tools when add-blocking, fast, feature-rich options like Safari and Opera exist?
Sadly, Apple users do.
Unless Apple can prove without question that it can handle any Web site with its final release of Safari, users should start to get very nervous and hope Opera and Mozilla developers take charge.
This misses the point entirely. The problem isn’t the quality of the browser, it’s the quality of the web sites themselves. IE for Windows has a ridiculously loose HTML parser that will interpret and display just about any garbage you care to throw at it. Since its market share is so high (more than 90% for many commercial web sites) lazy web developers write for IE rather than writing standards compliant markup. The only way a competing browser could render those sites in exactly the same way as IE would be for it to reverse engineer the IE rendering engine in its entirety, which kind of eliminates the point of having a different browser in the first place.
Safari’s most important feature (at least according to Steve Jobs) is its speed. This speed is achieved mainly thanks to a highly optimised rendering engine. If they were to add in enough code to completely emulate IE’s broken behaviour, the speed advantage would be gone.
What worried me is that a publication with more technical awareness than most could misunderstand the issues this much.
Incidentally, the only way this problem is going to get any better is through persistant advocacy to the many sites that have broken HTML. If a site doesn’t work in a modern standards compliant browser, tell them! The best way to do it is over the ’phone (if they list a number on the site) as that will cost them more in terms of customer service expenses, but a polite email to the right address is almost as good. If you don’t get a favourable response, the Mozilla Tech Evangelism team may be able to back you up (especially if the problem is with a major site)—see this page for details of their procedures.
And finally, if you develop sites yourself learn to code to the standards instead of coding for a specific browser. A one-browser web would be a very boring place indeed.
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