21–30 of 54 posts
This blogger spotted a talk at WWDC 2014 on WebGL. He speculates this means there's a forthcoming release of Safari with WebGL enabled by default, thus predicting Apple is embracing WebGL.
But we don't actually know that.
Wild speculation: iOS 8 will bring an out-of-process, heavily sandboxed webview, which was the missing piece for enabling webgl for everyone. The greatly increased attack surface (with almost direct gpu access via shaders etc) was too risky to host in in-process web views - explains why webgl was only enabled for iAds (since those would be vetted by a review team)
Would be nice to get something similar for in-app JavaScript JIT'ing.
Wild speculation: iOS 8 will bring an out-of-process, heavily sandboxed webview, which was the missing piece for enabling webgl for everyone. The greatly increased attack surface (with almost direct gpu access via shaders etc) was too risky to host in in-process web views - explains why webgl was only enabled for iAds (since those would be vetted by a review team)
> The greatly increased attack surface (with almost direct gpu access via shaders etc) was too risky to host in in-process web views What really? Were they seriously even pretending to use that excuse? Everyone I've ever talked to was 100% certain it was simply because they didn't want anyone by-passing the app store for games and other immersive content they would then have no control over. I'm not denying that webg…
This never made sense to me as an explanation, if only because for a very long time iOS had a far more sophisticated browser than Android; Android only really reached feature parity with Chrome for Android, and for years iOS was a much better platform for webapps. If they were so protective of the app store, they would hardly have put so much effort into best-in-class modern web support; offline web apps are in principle as much a threat to the app store as webgl stuff.
I also wonder when is Apple going to update Safari with WebRTC support. It's something many users could really benefit from.
Wild speculation: iOS 8 will bring an out-of-process, heavily sandboxed webview, which was the missing piece for enabling webgl for everyone. The greatly increased attack surface (with almost direct gpu access via shaders etc) was too risky to host in in-process web views - explains why webgl was only enabled for iAds (since those would be vetted by a review team)
> The greatly increased attack surface (with almost direct gpu access via shaders etc) was too risky to host in in-process web views What really? Were they seriously even pretending to use that excuse? Everyone I've ever talked to was 100% certain it was simply because they didn't want anyone by-passing the app store for games and other immersive content they would then have no control over. I'm not denying that webg…
I really hope WebGl+javascript kills CSS and html and all the other web stuff and we get back to desktop rich applications. And a URL can map to some state/object too. Google can then think about searching for things richer than just textual.
HTML and WebGL are mostly orthogonal. For example, you do not want to render text or form controls in WebGL.
We can improve HTML rendering with GPU-accelerated compositing, but that's mostly behind the scenes.
If Safari gets WebGL, combined with the new FTL JIT it could end up being pretty darn awesome for gaming.
I really hope WebGl+javascript kills CSS and html and all the other web stuff and we get back to desktop rich applications. And a URL can map to some state/object too. Google can then think about searching for things richer than just textual.
Not sure if you are trolling... HTML and WebGL are mostly orthogonal. For example, you do not want to render text or form controls in WebGL. We can improve HTML rendering with GPU-accelerated compositing, but that's mostly behind the scenes.
You don't. I don't. Our users don't. But trust me, there are plenty of ex-Flash devs out there positively ITCHING for a return to the days of un-navigable custom UI elements.
I really hope WebGl+javascript kills CSS and html and all the other web stuff and we get back to desktop rich applications. And a URL can map to some state/object too. Google can then think about searching for things richer than just textual.
Not sure if you are trolling... HTML and WebGL are mostly orthogonal. For example, you do not want to render text or form controls in WebGL. We can improve HTML rendering with GPU-accelerated compositing, but that's mostly behind the scenes.
I am thinking of something like the LivelyKernel[0] or better.
Earlier quoted context omitted.
> The greatly increased attack surface (with almost direct gpu access via shaders etc) was too risky to host in in-process web views What really? Were they seriously even pretending to use that excuse? Everyone I've ever talked to was 100% certain it was simply because they didn't want anyone by-passing the app store for games and other immersive content they would then have no control over. I'm not denying that webg…
> Everyone I've ever talked to was 100% certain it was simply because they didn't want anyone by-passing the app store for games and other immersive content they would then have no control over. This never made sense to me as an explanation, if only because for a very long time iOS had a far more sophisticated browser than Android; Android only really reached feature parity with Chrome for Android, and for years iOS…