2 ms·

The list of fatal regressions both chrome and firefox have introduced is pretty close to 0, developing a new version of a web app every 3 months for both browse

The list of fatal regressions both chrome and firefox have introduced is pretty close to 0, developing a new version of a web app every 3 months for both browsers is beyond obtuse to the point of outright lying. Web developers arent as utterly hopefully as you seem to think, my gmail supports drag and drop attachments, my irc client supports websockets when available, my task tracker works offline (and on a mobile), my maps support geolocation. And I personally dont support have to support ie6, but a lot of people still have to. I havent heard of anyone that has to support Chrome v1.

Silhouette 15y ago
> The list of fatal regressions both chrome and firefox have introduced is pretty close to 0 Well, if they've only introduced a few here and there, I suppose that's OK then. </sarcasm> > developing a new version of a web app every 3 months for both browsers is beyond obtuse to the point of outright lying. It's a good thing that's not what I said then, I suppose. > And I personally dont support have to support ie6, but a lot of people still have to. A few people still have to, I'm sure, but the market share has dropped like a stone over the past year or two. For most projects that aren't in-house jobs in the organisations that haven't managed to leave it behind yet, it is no longer relevant.