Sometimes, Life really does turn around and bite you on the ass. Regular readers will know that back in the summer I had a stroke. Since I was released from Hospital care things had been going a lot smoother. I got married, I went back to work, and life in general was getting back to normality. Until yesterday morning, that is.
On Monday morning, before I started getting ready for work, I had an epileptic seizure (dislocating my shoulder in the process). Just as I thought everything was getting back to normal, this comes along to throw a spanner in the works…
At the end of the week I need to get a battery of tests done. Until then, the hospital are trialling me on some medication to try and prevent any repeat episodes.
It really sucks that until the tests are done, I’m not going to know how how any of this is going to potentially effect the rest of my life.
For something different to do on a Friday night, Nicola and I went to see the new Harry Potter film on Friday. Both of us thought it was very good. Ron’s brothers, Fred and George are hilarious. I was a little dissapointed with the cut of the film; it was so fast-paced that a lot of stuff got left out—stuff that is important later in the series (Harry learning the story of the Longbottoms from Dumbledore, for one… it was glossed over far to quickly for my liking.). To be fair though, they did have a lot of material to cram into a 2h 15 min movie! Over all, it’s a good addition to the series and if you’ve enjoyed the previous films you’ll love it.
I know, I know, in theory we should be developing sites that work in every browser and not just targeting specific applications. However, the reality isn’t quite there yet. Support for the different web standards varies massively from vendor to vendor.
Usually we make the decision on how much effort we put into making a site work in a particular browser down to the visitor statistics of that site. If your site only receives a handful of visits from a certain browser, why spend hours – or even days – trying to work around its faults?
So my question is this: just how low should the numbers be before a particular browser gets ‘cut off’? Take, for example, the top 5 browsers in Pixel Meadow’s Mint logs:
- Firefox (54%)
- Safari (31%)
- Internet Explorer (8%)
- NetNewsWire, Camino & Opera (2%)
- Shrook (1%)
From those numbers it’s clear that I need to support Firefox and Safari (which by extension means support for NetNewsWire and Camino), but what of IE, Opera and Shrook? Do I go out of my way to make sure any future revisions of Pixel Meadow work fully in these browsers, or do I just make sure they’ll degrade gracefully if need be?
Of course, this is assuming an existing site… It stands to reason that a new site with no clear visitor demographics should target as wide as possible until their visitor statistics are known.