| "Safari is rapidly getting a reputation as the new IE6." And that is just a ridiculous comparison done by people who have never witnessed that period or are having a different agenda. One of my first jobs (more then a decade ago) as a young developer was being a web developer for an American/Belgian e-commerce site. One of the things that was very important - because every customer counts - that the site displayed and worked perfectly in any browser (IE6, FF/Mozilla, Safari and Opera at the time) That was a situation that wasn't a lot of fun because you had standard HTML that more or less worked in any browser with the exception of IE6. There where a lot of moments that I really hated my job because of the frustrations that IE6 often brought to the table. That is in no way comparable with Safari today. And while I would like to have Apple more rapidly implementing new API's, with IE we could only dream of having an IE version that got new features every year. Years have we have witnessed the fallout of IE6, that will never be the case with Safari to this day. IE6 was a vehicle to create an internet that only worked with Microsoft standards so that others couldn't be a valid alternative hence the IE6 markup vs the rest. You can't do that by dragging your feet when implementing API's, you only price yourself out of the market in that way. |
It is like with CSS 10 years ago. This nice new CSS feature (HTML5 API) which would perfectly solve your problem? Sorry you can't use it because IE (Safari) does not support it (maybe never will).