Now this is what I'm talking about, woohoo! Screw you corporate non updaters!Quote:
Originally Posted by xxMATTGxx
Printable View
Now this is what I'm talking about, woohoo! Screw you corporate non updaters!Quote:
Originally Posted by xxMATTGxx
Found your reason, WebGL is/was riddled with security flaws and actually wasn't a standard (or was very early on) upon IE9's release.Quote:
Originally Posted by HotelUser
http://news.cnet.com/8301-30685_3-20...l-to-security/
http://blogs.technet.com/b/srd/archi...d-harmful.aspx
http://arstechnica.com/information-t...ecurity-needs/
http://www.netmagazine.com/news/webg...es-highlighted
Clearly the security concerns are of such critical importance considering the other two major browsers support it.Quote:
Originally Posted by Recursion
IE9 is actually causing IE's usage share to start rising again in some locations.
That is the problem with slow release cycles, you can't adapt to a fast changing environment that the world of web standards is becoming. Also in terms of large companies I don't see why they can't adapt to dealing with frequent updates either. I automate browser tests (http://seleniumhq.org/) to check my code is working properly. Why can't you flip this over and use it to check that the new version of the browser works with your corporate web based tools/sites? Only takes a few minutes to run and it is likely that these tests or similar have already been written by the developers if it is a large scale project.
The issues in WebGL have been resolved and the only possible issue is that depending on what OS you run then malicious WebGL code could freeze your computer (Win 7 and Linux handle this fine with resetting of the graphics card driver when it locks up, only mac os x fails iirc) and if MS chose to there is no reason why they could not implement it today. In my opinion the reason they are not implementing it is because WebGL is maintained by the same people who do OpenGL which competes with DirectX.
Quote:
Originally Posted by Recursion