51–60 of 650 posts
Will it be patent encumbered, like Apple's "proposal" for touch events API? > Meanwhile, GPU technology has improved and new software APIs have been created to better reflect the designs of modern GPUs. These new APIs exist at a lower level of abstraction and, due to their reduced overhead, generally offer better performance than OpenGL. The major platform technologies in this space are Direct3D 12 from Microsoft, Me…
Hey Apple, how about developing your browsers to support modern web technologies first?
Earlier quoted context omitted.
Wait... what? Deceptive... really? Come on now. http://caniuse.com/ In terms of tracked features they're ahead of Edge with both their stable release and in development (TP) builds. Don't let your own prejudices distort reality.
http://caniuse.com/#feat=notifications Every. single. other. browser. Including desktop Safari.
http://caniuse.com/#feat=es6-module
Like I said, "ahead of the game in a lot of areas", not every area.
Earlier quoted context omitted.
Wait... what? Deceptive... really? Come on now. http://caniuse.com/ In terms of tracked features they're ahead of Edge with both their stable release and in development (TP) builds. Don't let your own prejudices distort reality.
http://caniuse.com/#feat=notifications Every. single. other. browser. Including desktop Safari.
I hate websites trying to give me notifications. I like that I don't get stupid prompts from mobile Safari about that kind of thing.
Earlier quoted context omitted.
Wait... what? Deceptive... really? Come on now. http://caniuse.com/ In terms of tracked features they're ahead of Edge with both their stable release and in development (TP) builds. Don't let your own prejudices distort reality.
http://caniuse.com/#feat=notifications Every. single. other. browser. Including desktop Safari.
IE: Not Supported
Opera Mini: Not Supported
Chrome for Android: Not Supported
The API looks like a direct port of Metal to JavaScript.
Also, Metal was announced June 2014, released September 2014. Vulkan was announced March 2015, released Feb 2016.
I don't see any reason for favoring Vulkan specifically for Web when compared to Metal I can read: "Metal still does a lot of hand holding and behind-the-scenes management for you, while with Vulkan you are responsible for — literally — everything. And man they were NOT kidding when they said that the API is explicit. Its actually quite ridiculous how difficult and detailed the API is." (1)
We need concise, clear and coherent code.
Earlier quoted context omitted.
> As someone who spends a lot of time in that space I don't really see what this is solving, WebGL is good enough and anyone serious about performance/compute are going to drop down to native anyway. Not true at all; if your primary performance bottleneck is the GPU code, not CPU code, you could use a better web API modeled after Vulkan, for the same reason people switch from GL to Vulkan. In general, if there's ever…
As soon as you clear up that GPU bottleneck guess what's going to be your next one? (Here's a hint, it's the thing that's dispatching to your GPU). Another aspect that scares me about this is the security implications of exposing compute to the browser. Esp when you start talking about unified memory architectures. There's been more than a few exploits from a clever soul calling glReadPixels in the right circumstance…
I feel like Apple are just trying to get in early with a proposal so they don't get forced into supporting Vulkan (and wasting all that effort on Metal). Mind you, it does at least look like they're trying not to be jerks about it (even if the motivation is somewhat selfish). They specifically mention the competition to Metal and how "webgpu" is ideally an abstraction that'll sit on-top of Vulkan, Metal and Direct3D…
Is that really a "just" or is it the right thing to do? Working on top of all the major APIs is the right thing for the web. We've discussed our proposal a lot with key players in this space (including other browsers, GPU vendors, relevant ISVs) and we're pretty sure a cross-API abstraction is the way to go. Some even want to build a form of cross-API abstraction at the native C/C++ level.
The end goal is to maintain Metal as a proprietary bit of tech for native apps, in order to make it more burdensome for people to port native apps away from the Apple platform and as a result give Apple more exclusive apps and more artificial barriers to entry for competitors. Why should the web standards people be bending backwards to support that goal?