| First, I tend to agree that the Microsoft bashing is a little overdone. They've been moving forward legacy code for a product that now is by far the oldest browser in the field while at the same time having to support an obviously enormous user base. They've made their cost vs. timeliness vs. goodness decisions as is their right to do so. We make the same decisions about IE compatibility work. Being a very early stage startup, we figure two things: 1) The field of IE users has a lower percentage (and perhaps absolute number) of potential early adopters. For our app, this is a dead certainty, although it is not necessarily so for other apps. 2) IE users, who aren't constantly comparing how a site looks in IE against how it looks in other browsers, are accustomed to things being a little off from time to time. This is their IE world. So our acceptance level at this stage is does everything work and does it look basically ok in IE. We don't sweat a lot of the finer stuff, again, figuring most of the the IE users are in a world where things are off by a few pixels here and there and don't get too upset by it. If they did, they'd be on the other browsers, where the sun shines a little brighter and the birds sing a little sweeter for all websites. That is the important point to remember - browser type users are self-selecting in their tolerance for UX hiccups. |