41–50 of 54 posts
Earlier quoted context omitted.
Electrolysis is NOT sandboxing, full stop.
To cite the wiki: "sandboxing the content processes is a separate project from Electrolysis". So Electrolysis lays the foundation for sandboxing.
Earlier quoted context omitted.
We were talking about this yesterday. I asked how many of the previous issues we classified a security problem would of been mitigated by a sandbox and the conclusion would be that it would not even cover the majority. Most of the security issues we encounter are with bugs in the driver. A common bug for example with the Intel mac driver is when sending allocating a valid large texture the texture will sometimes inst…
I thought webgl didn't have glreadpixels?
Right now implementing an HTML5 or JavaScript multiplayer game is still a considerable exercise in navigating browser differences.
So I will be satisfied even if Apple can only solve the most of these problems on desktop platform and make it on by default.
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)
I wonder if Firefox will remain the only browser out there without a process sandbox. It's still the most vulnerable browser because of that: http://www.extremetech.com/computing/178587-firefox-is-still...
"... The [Servo] engine processes will use the operating system sandboxing facilities to restrict access to system resources."
The title is misleading. It should read, "There's a WebGL talk at WWDC 2014." 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.
The HN guidelines call for changing titles when they're linkbait or misleading.
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)
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 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 hope their screening will remain strict. I foresee a whole wave of... "quality titles" scripted in JS.
What screening? WebGL is used on... the web. That's the beauty of it.