Why? We can already play AAA games on our computers. It works very well, much better than anything web-based. Why would anyone put effort into replicating the same thing inside the browser?
This is much more important for indie devs than AAA devs though (the current problems of the web platforms are not really 'AAA specific').
Also, don't forget that PC gaming could very well have died out during the transition from DOS to Windows without Microsoft actively supporting game development on Windows (with the DirectX APIs), without this, AAA gaming could very well be console-exclusive now.
Agreed, however platforms that restrict app distribution also heavily restrict what you can run via the browser (see Ios). So the benefit is minimal.
> a space to try out quirky new ideas
This has nothing to do with web. Look at steam's catalog. Plenty of whacky quirky stuff is available.
> no lengthy download or installation process for instance
Why do you think AAA games will not need downloading assets and logic?
> This is much more important for indie devs than AAA devs though
I agree, but this is a solved problem with Steam. No need to develop your own over the web.
As internet connections get faster it makes sense to stream/prefetch data directly from CDNs as needed instead of downloading everything upfront.
> Look at steam's catalog. Plenty of whacky quirky stuff is available.
Agreed, but that's the exception, not the rule. Look at Apple's app store ecosystem for a counter example where apps and developers are banned on Apple's whim. This couldn't happen on the web.
https://github.com/gpuweb/gpuweb/issues/566
Basically. Rather than doing something better w3c is designing by committee so hard it somehow made worse OpenGL.
A fellow contributor, that had to deal with pain of OpenGL, laughed this shit out of the gate.
And I mean look at it. Who in their right mind looked at that and said, yeah that looks decent.
Basically bunch of stuff listed in that blog are Rust specific uint vs int.
Others are kinda standards problem of undefined behavior being well - undefined. Gamedevs are used to this, but not Rust devs.
I'm reminded of xkcd https://xkcd.com/927/
So rather than relying on previous work, they wrote their own somehow ugliest standard.
- Not knowing you need to have entry point for the shader to be executed.
- kvark's complaint about OpFmod being misnamed are kinda missing the point, % isn't the mod operator but remainder operator (in C/C++)
- https://mobile.twitter.com/TheSpydog/status/1232819839888166... You know it's a pretty bad idea when Unity and Adobe are begging you not to do this.
- I mean what you prefer to write?
GLSL:
int a = 2
for (int i = 0; i < 4; i++) {
a *= 2
}
WSGL: const a: i32 = 2;
var i : i32 = 0;
loop() {
break if (i >= 4);
a = a * 2;
continuing {
i = i + 1;
}
}I'm also really not sure how you got the first point from what he wrote. He was not saying he was surprised to find "you need to have an entry point" he was saying the restriction made no sense, and that existing tools didn't even take advantage of having more than one entry point due to driver bugs.
The rest of your points are basically just opinions masquerading as something else. In any case I don't actually care how hard WGSL is to write, because I don't have to write it (you can go through a translation layer). What I'm not going to do is pretend that SPIR-V is a great choice for this intermediate layer solely on the basis of what I've heard from other graphics people who haven't actually tried to use it for that purpose--which is exactly what the article is about.
> he was saying the restriction made no sense
So presented with reality of a complex, buggy drivers, his solution is - to ignore it? Wow imagine in UTF-8 people just said, yeah 8bit 0 are ok everywhere and caused hundred of billions of lines of code to be written to deal with null mid UTF8 stream.
> I don't actually care how hard WGSL is to write
Awfully dismissive. Well, ok, you won't have to write it but someone will. And those someone are going to curse whoever wrote that abomination of a spec.
A spec that: - That doesn't respect backwards compatibility - Looks like pure torture to write in - Misunderstands some part like OpRem
I'm not very confident in it to be honest. Looks to me just another overly elaborate moat for browser implementors.
That didn't help the large move to mobile gaming by its primary audience (which I'm guessing was teens).
Towards the end Kongregate became a platform for idle games that pushed users hard towards pay to win. Sucks, but they grew huge off the glory days of ad revenue and I presume they had to do something to keep surviving.
This can change very quickly if there's actually some breakthrough web game, but that hasn't happened so far, and nobody wants to be the first to take the risk.
That's not correct though, the game runs on a Linux box in Google's datacenters (granted, from a business perspective that's nitpicking - but not quite, see below, but it's a massive difference from a technical perspective).
Scaling to large audiences is much more expensive with the game streaming approach though (but we'll never really know because Stadia bombed, just as all other game streaming platforms before).
You want one browser vendor to implement a proprietary API and then have the ramining vendors try to emulate it?
But apart from that, Microsoft was in a unique position to dictate standards to GPU vendors, as draconian as it sounds, this worked much better than Khronos' design-by-committee approach in OpenGL.
This has been promised since at least the WebGL and asm.js days. It still won't happen, but not mainly for technical reasons, but for business reasons.
...but of course also some technical reasons. Asm.js/WASM and WebGL/WebGPU are fine, but most other web APIs are a mess and the web is a highly unstable platform, APIs are deactivated or deprecated on a whim, APIs change behaviour unpredictably, behaviour differs between browsers, etc etc...
TL;DR: the web needs a proper "DirectX initiative" like what Microsoft did in the late 90's to get Windows gaming off the ground.