#Minecraft opengl 2.0 download portable#
#Minecraft opengl 2.0 download code#

> Yes it is a very bad thing, when Vulkan can keep using GLSL and HLSL, while DX12 happily will use any HLSL from the API history, and Metal can use proper C++14 shaders. > Intel had two failed attempts to bring compute into the browser.

#Minecraft opengl 2.0 download portable#

The goal is to provide modern standardized tech to developers, and it does it in a portable way, which makes it even more affordable. We're not talking about bringing the bleeding edge GPU tech to the web (it won't, it's never standardised anyway, like Mesh shaders you talked about). Even AAA games released this year support GPU released in 2012! For non AAA games, targeting a 5-years old API is probably the newest you can afford. Most games released in 2017 had to support hardware from 2012 anyway. > Even if Apple had done it on time, it was a 2012 hardware API for 2017 hardware Of course, I can't be 100% sure that Apple won't change their mind (like they eventually did for WebGL2) or anything, but there is no reason to believe they'll do so.

> What guarantees do you have it won't happen again?ДЄpple was pretty clear about their intent not to ship WebGL2, and they did the opposite for WebGPU so it's not gonna be the same story.

#Minecraft opengl 2.0 download code#

One can just as easily hop into their code and add your own extension to make use of Mesh shaders in DX12, I can say that at least Dawn's codebase is set up to allow for such extensions from what I've seen. I can use some very specific new features' that's totally true, but you can do that with WebGPU native too: after all, Dawn and other WebGPU implementations are just abstractions over those 3 APIs. If you want to argue 'but by dropping to the level of DX12, Vulkan, Metal, etc. Separately, AMD doesn't support mesh shaders in Vulkan either, in fact Vulkan doesn't at all outside of a Nvidia extension from what I understand - and it sounds like there are some concerns from Khronos about whether they even map to all GPU architectures in a reasonable way at all. Despite its name, WebGPU is actually pretty much a 1:1 mapping of what is commonly available across APIs.

WebGPU is focused on landing 1.0 currently, so yes, more features are not on the immediate roadmap.Д«ut they've been considering/investigating adding support for this before mesh shaders in DX12 were even finalized so it's not like there is some 'we cannot / will not expose that functionality' mandate going on here. I'll say I am definitely biased in favor of WebGPU up front.