Jan 25, 2005, 12:32am EST
While those are valid reasons on both side, I think an important point was overlooked: supporting Safari makes it easier for everyone to move away from Internet Explorer. Obviously, people who already use Safari as their primary browser have already moved away from IE so they aren’t the people that need to be converted. On the other hand, some users may avoid using Safari, or worse, all Macs because some webpages don’t work. This mentality may prevent the user from trying alternate browsers because of the belief that IE always works while other browsers don’t.
As web developers, I believe that it is our responsibility to try to break this myth. I’m not saying this because I’m some Mac zealot or because I love Safari (I’m not even sure I like Safari), but because I think this opens up opportunities for all alternate browsers, including Firefox. It puts the notion into people’s head that they don’t have to use IE to get a rich web experience; any browser will work and some might even be better than IE.
 Of course, an implicit assumption is that not using IE is a good thing. I don’t think I need to argue that point here and now.
Doug at Mar 24, 2005, 11:47am EST
Isn’t the idea that if browsers are standards compliant, you only have to make one set of code? So you tweak your code to work in IE because it has the largest install base. But you don’t tweak your code for flaws in otherwise standards-compliant browsers because the assumption is those browsers will eventually catch up with you; not the other way around, right? (This is written by someone with minimal coding experience who has never had to make such decision.)