3 ms·

Chrome and Firefox don't support features within moments of someone conceiving them. I've seen discussions about what features will be coming to Chrome in the f

Chrome and Firefox don't support features within moments of someone conceiving them. I've seen discussions about what features will be coming to Chrome in the future - rarely does a feature take less than six months to go from idea to stable implementation in Chrome. Firefox is a little different because Mozilla is pumping APIs into Firefox OS and then moving them to the main Firefox browser. IE has issues with implementations even with their slow release cycle, as does Safari. While in theory a quicker release cycle probably should result in less stability and more bugs, there doesn't really seem to be this correlation in practice. A good way to check this out is to have a look at caniuse.com and see which browsers have issues with feature implementations (although caniuse is lagging behind a bit of recent). IE, Firefox, Chrome and Safari will all have issues. To Apple's credit, Safari is the only browser which seems to be willing to regularly remove buggy features.

Silhouette 12y ago
While in theory a quicker release cycle probably should result in less stability and more bugs, there doesn't really seem to be this correlation in practice. Anecdotally, the bug tracker for every major project I currently work on would disagree. That's a fair range of projects, using very different sets of browser features but including quite a few relatively recent developments. A good way to check this out is to have a look at caniuse.com and see which browsers have issues with feature implementations Caniuse is great, but it's not even close to the level of detail I'm talking about here. For example, it currently lists no known issues with HTML5 video elements, where IIRC one project I work on that uses that feature extensively was tracking 17 related open issues as of a few days ago, including at least one for every major browser. When I write about that kind of experience, I sometimes get asked why we don't do more to support the browser developers by filing detailed bug reports when we find these issues. Sadly, the answer is simple: the projects I work on all have relatively small teams and would literally have to hire another full time employee just to report browser bugs, because we find that many. And a heavy majority of them are in Firefox or Chrome.

Silhouette 12y ago

While in theory a quicker release cycle probably should result in less stability and more bugs, there doesn't really seem to be this correlation in practice. Anecdotally, the bug tracker for every major project I currently work on would disagree. That's a fair range of projects, using very different sets of browser features but including quite a few relatively recent developments. A good way to check this out is to have a look at caniuse.com and see which browsers have issues with feature implementations Caniuse is great, but it's not even close to the level of detail I'm talking about here. For example, it currently lists no known issues with HTML5 video elements, where IIRC one project I work on that uses that feature extensively was tracking 17 related open issues as of a few days ago, including at least one for every major browser. When I write about that kind of experience, I sometimes get asked why we don't do more to support the browser developers by filing detailed bug reports when we find these issues. Sadly, the answer is simple: the projects I work on all have relatively small teams and would literally have to hire another full time employee just to report browser bugs, because we find that many. And a heavy majority of them are in Firefox or Chrome.