|
|
|
|
|
by drewmclellan
5155 days ago
|
|
The web, like anything, has costs and benefits. A big benefit is that you and develop and deploy an app once, centrally, and anyone can access it from anywhere, on any sort of web device. The cost of that is that you can't control how they're accessing it. To have the benefit, you have to accept the cost. By shirking the cost of providing even some level of support for IE, you're ditching the benefits afforded to the part-time copywriter who needs to stay at her desk and work her lunch hour during the office job she keeps to make ends meet. You're ditching the benefits afforded to the business owner on the road whose laptop won't join the hotel wifi and has to use the hotel's "business center" to issue the invoice needed to meet his mortgage payment. You're ditching the benefit of a happy customer evangelising the product to a colleague, and wanting to give them a quick demo by logging in on whichever laptop is currently hooked up to the meeting-room projector. The times when a user doesn't have control over their environment are the times when they need a product to come through for them the most. Especially when that product is their means of getting paid. Not being able to offer "amazing things with canvas" to IE (or any browser) is okay. Not offering support to be able to log in and perform a set of basic key tasks from any browser whatsoever is, to my mind, throwing away one of the biggest benefits the web can offer as a platform. |
|