May 19th, 2009
A decade into a career working with computer stuff, I still don’t get why anyone would write a broswer-specific website. Ever.
It isn’t a rule of thumb, it is simpler logic than that:Â Don’t limit your audience.
One of the things Iam not saying here is don’t reach forward to embrace new features and capabilities. Although that may happen, I garuntee you can still get your message across and your application built without it. All that has been done since the days of HTML 1.0 is to increase whiz-bang features and client-side processing. It may not be as easy and your cheap, wet-behind-the-ears programmers may not like that you’re not using their new favorite language, befuddle 4.0, but you can get your message across and your application built without ostracizing any chunk of your audience because they don’t use your favorite browser. Even Opera, even Safari, even the blackberry browser if you need to.
But for fuck’s sake don’t restrict your audience to only using Internet Explorer.
And yes, I’m looking at you, Research In Motion. Your BlackBerry upgrade site has a link that suggests Mac users should follow, which takes me to a page that informs me the information can only be seen using IE. WTF?
I’m ranting here, fine. If the frustration persists or the discussion warrants I may flesh this out more later.
I encounter this predominantly in intranet situations. I suppose it is the lingering assumption of corporate IT departments that they control the desktop (ha!) and therefore limiting access to their supported client(s) is okay or even smart.  I’m here from the present and I’m here to tell you that you don’t control the access client (or if you do, you spend an inordinate amount of energy trying to maintain that control), and I just got a postcard from the future informing me that all clients will be user-owned by lunchtime.
Veering off onto a well worn yet tangential path, let me remind you that the pendulum swing between centralized and decentralized computing resources is regular and predictable, and the move back toward centralization is picking up steam.  The users are still forming two orderly groups: powerless and power users. The powerless want to be provided with the tools to do their tasks, the power users want to use their tools to do work.  For the powerless you’ll soon be providing something like a remote desktop or thin client that runs from a single application on their corporate-run endpoint, for the power users you’ll soon be providing an option for a remote desktop that runs from a single application on their user-run endpoint or a suite of applications served over defined protocols (SSL, HTTP, IMAP, SSH, etc.). And this is really where the rub is. Not because I’m a power user and it ties my hands, but also because it ties the hands of those who would make use of their best tools.  For example (and to bring this back around), if you don’t like IE for some reason, you should be able to use Firefox, Safari, or Opera because they all do the task of communicating via HTTPS. The P in that acronym stands for protocol, which means a “standard procedure for regulating data transmission between computers.”  If Safari doesn’t do it properly, Safari is broken and needs to be fixed (not blocked based on the user-agent string).
And I don’t feel one bit better after this rant, so this has been a colossal waste of time. Ah me.
Filed under:
Computers,
rant,
Workstation
No Comments »