Linked by Thom Holwerda on Fri 14th Dec 2012 11:51 UTC
Thread beginning with comment 545285
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
You really need to call up and tell the caniuse.com guys about all the ways in which they are wrong
They don't even say how or against what the tests where performed. That alone is unserious. They eg say Apple iOS Safari does not support WebGL but failed to note that it does for selected websides or if you apply something like http://demoseen.com/webglenabler/ for all.
WebGL was added to iOS 4.2 for iAds but Apple has not yet turned it on for general browsing and the like
So iOS does not support WebGL, and a vast, vast majority of phones don't support WebGL because Chrome is far from being the majority browser on Android.
Speaking of de-facto, WebGL is de-facto absolutely nowhere.
Besides, Khronos isn't part of the W3C, and thus their WebGL isn't a fucking standard.
The fact that they're a direct competitor to DirectX, and then people have the nerve to question why Microsoft doesn't cede ground to a direct competitor is ridiculous.
If you want a palatable standard for 3D on the web, you're either going to have to make it agnostic to the underlying rendering technology, or not take anything at all.
Microsoft will not capitulate to WebGL, it runs counter to their entire strategy with DirectX, for dubious gain.





Member since:
2008-08-09
You really need to call up and tell the caniuse.com guys about all the ways in which they are wrong: http://caniuse.com/webgl . Now, in the event that you are just making shit up to support an already poor argument I guess webGL is not anywhere near a de-facto standard on mobile after all. Either way; Google does not use it for any of their mobile pages, and this whole line of argument is pointless.