This is one of those unpublished posts I told you about. I don’t know why it wasn’t published (well, except that I hadn’t written the last couple of sentences).
A while back I heard the strangest ever request from a customer.
As you might know, I work for a software house.1 We write financial software for banks. As a thing to talk about it tends to be boring, but it can have interesting challenges.
Anyway, one of our product’s problems, as a web-based app, is that it was written to specifically target the Internet Explorer browser.
I know that seems at best charmingly retro, and at worst appallingly non-standards-compliant, but there are a couple of good-ish reasons. Principally the fact that the original version of the web app was written by contractors who both only knew IE, and were told that our clients only cared about IE. The latter was probably true at the time, and as for the former, well: let’s just say that sometimes people in companies make some stupid decisions, and leave it at that.
Inevitably, and especially as the browser landscape has matured and Apple and Google have come to rule the world, there have been calls to fix things. But there have always been higher-priorities. Getting new features done takes priority over making things work better, sadly.
One of these years we’ll fix it — personally I don’t think it’ll be as difficult as people always think (that fear is another reason why we have resisted doing it).
But what it would really take to force us to sort it out would be if a client demanded it.
If it were going to make or break a sale, we’d be all hands on deck.
So it’s interesting that we got a query a while back wherein a client was concerned about the fact that the app doesn’t work properly in Firefox. This was causing some of their users distress, as FF is their chosen browser. Was this it? Was this the opportunity, at last, driven by customer demand, to bring our app into the late twentieth century?
No, the client had a better idea. They wanted us to to change our app such that it would detect that the user was running something other than IE…
… and prompt them to use IE instead.
(We didn’t agree to their request.)
Incidentally, why “house”, I wonder? By association with “publishing house”, obviously, but why are those “houses”? I’m reminded of a discussion I had on a software mailing list in the nineties regarding the American tendency (then, if not now) for referring to a “shop”, meaning a programming entity, including an old-school IT department within a company. ↩