3 ms·
It feels pretty good to click the link on my iPad and see the leaves. Apple was the last hold out for WebGL. Hopefully, we'll see a big spike in WebGL usage.
by melling 12y ago
It feels pretty good to click the link on my iPad and see the leaves. Apple was the last hold out for WebGL. Hopefully, we'll see a big spike in WebGL usage.
- foobarfizzbuzz 12y agoCan you please explain how Apple was the last to hold out for those of us who are ignorant on WebGL.
- uptown 12y agoThey only recently added support on iOS devices: http://caniuse.com/#feat=webgl http://caniuse.com/#feat=webgl
- robin_reala 12y agoIt was disabled by default on desktop before Yosemite too.
- robin_reala 12y agoMozilla were the first to implement (Vladimir Vukićević’s work) with Opera around about the same time. Chrome jumped on board a few years later, and IE as of version 11. Apple was the holdout for basically unknown reasons (they’ve had a working version preffed off for ~5 years now) but the basic assumption is that graphics card drivers needed to be hardened to provide a secure execution environment for shaders. It’s one thing to buy a game and give it root, quite another to load a webpage that could start a WebGL process in the background and load executable code onto the graphics card.
- acdha 12y agoSecurity is definitely the likely candidate (it was for Microsoft as well): even on Yosemite, where they enabled WebGL by default, there's a per-site permissions interface similar to things like location services access.
- pjmlp 12y agoIt is still pretty limited on mobile devices. On my S3 I have to enable it on Chrome and most people are using the native Android browsers. On my Windows Phone, my 3D samples turn into a wireframe models.