So there's a bunch of excitement about this WebGPU business...

Can somebody point out a "hello world" (render a simple triangle or cube, maybe) example that's just plain 'ol Javascript?

Not Typescript or other languages "compiled" to Javascript. Not using a bunch of libraries, frameworks, or middleware. Not requiring Node or a build system or other special tools.

This is The Web, right? I don't *need* all that junk to just make use of this new API, right? Right?

#webgpu #webdev #questions

-- signed, an old fart who started flipping through the docs and sighed at a bunch of async/await business because, really, do we have to obscure flow control just for the sake of terser source code that's harder to read an reason about?

Follow

@swetland

First, there were no asynchronous operations, but we needed them for calling servers (and later other things). So callbacks were invented to have them.

But callbacks got us into callback hell, so promises were invented to abstract them. There were 3 different incompatible kinds, but it seems nowadays we are finally settling on the one and only.

But promises still were not really intuitive, so async/await were invented to hide them under syntactic sugar.

But async/await It is a incomplete abstraction, because you have to create promises anyway. And yes, newbies find it easier, until they are forced to create a promise and they don't know what it is. Besides, being forced to mark an old function as async only because you just added a line with the word 'await' is not so great, really.

So the countdown for the next abstraction begins...

May the documentation chaos ensured by never finding an example using your favorite abstraction not bury us all.

Sign in to participate in the conversation
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.