The point of standards is to regulate competing implementations. It's widely understood that competing standards = BAD (and they exist far too often in far too many industries, to their detriment; also, see this mandatory XKCD reference http://xkcd.com/927/ ) and competing implementations = GOOD (the alternative is an IE6 situation, which we're fast moving towards again with WebKit).
I wonder how much this has to do with the average age of web programmers. With a development-community with such a short-term memory, I wonder will the inability to learn from past disasters (like IE6) lead to endless recursion...
All of the people commenting "Apple HAS browser competition!" may not be correct (they are just Safari skins) but neither is the OP.
Dolphin, Sleipnir, Maxthon are all available on iOS in *the same* incarnation as on Android - as skins of the stock engine. The fact is - while many might criticise Opera and Firefox for various reasons, they're the ONLY two mobile browsers actually competing with stock offerings.
Slashdot Mirror
https://github.com/feross/filldisk.js/issues/7
The point of standards is to regulate competing implementations. It's widely understood that competing standards = BAD (and they exist far too often in far too many industries, to their detriment; also, see this mandatory XKCD reference http://xkcd.com/927/ ) and competing implementations = GOOD (the alternative is an IE6 situation, which we're fast moving towards again with WebKit).
Here's an interesting article on the amount of *postitive* support there was from web developers for IE6 when it first came about... which does give me a strange sense of deja vu, even if the author of that particular blog post wouldn't agree.
I wonder how much this has to do with the average age of web programmers. With a development-community with such a short-term memory, I wonder will the inability to learn from past disasters (like IE6) lead to endless recursion ...
'grats. Full marks in all three.
Afterall, Github's been proven to be a utopia of wise, well-informed developers who know exactly what best practices are w.r.t. releasing files into the wild
All of the people commenting "Apple HAS browser competition!" may not be correct (they are just Safari skins) but neither is the OP.
Dolphin, Sleipnir, Maxthon are all available on iOS in *the same* incarnation as on Android - as skins of the stock engine. The fact is - while many might criticise Opera and Firefox for various reasons, they're the ONLY two mobile browsers actually competing with stock offerings.
The OP mentions Dolphin Jetpack which is - according to Dolphin - a plugin "which provides extensive canvas/GPU/JavaScript performance enhancements". How they do this is not mentioned anywhere on the web I can find, which is somewhat odd. Standard issue Dolphin wraps the phone's stock Webkit - if they're including some new updated Webkit fork packaged into the Jetpack plugin, then where's the source-code? Isn't Webkit supposed to be open source?