Jonathan Blow

From now on, any time I am reviewing programmer resumes for a job, if I ever see "WebGPU Working Group" on a resume, that resume goes instantly into the trash. Not bluffing. There has to be a penalty for pollution or people will keep doing it. I encourage others to treat resumes

What's the solution you're thinking of? A good portion of the group fought for SPIR-V for years, Apple fought back with some alright reasons, they settled on a language that's really straightforward to translate back and forth to SPIR-V.

The problem is why can't I just program in whatever language I want, like we knew how to do in the 1970s, then gave up that capability for some reason. Re SPIR-V, come on, the corporate politics there are clear as day. You know they wouldn't "fight back" against MSL, even if

So given that the WebGPU developers don't have any influence over OS GPU abstractions, do you think they should have given up and not made anything, or write compilers that can accept all major shading languages on any OS, or are you saying SPIR-V?

I think they should work to fix the actual problem, which is that browsers are lame.

Okay so if nobody should work on abstracting GPU APIs in browsers, what about native? Given current APIs as fixed, do you endorse efforts to try to write a hardened abstraction over them, or just give up and everyone writes for each platform manually?

I think we should do what we did in the 1970s, which worked much better than what we are doing today.

But that's not an option if I want to program GPUs today. I want a CPU-style toolchain straight to machine code for major GPUs cross-platform too. But that's not an option unless I form a decade-long conspiracy of friends to become execs at Apple, MSFT, AMD, Intel, Nvidia...