Greggman

hacked in a fix. No idea how fragile it is. The code is a mess but no time to refactor

given an id (from the URLs) you can get them with ``` const req = await fetch("https://www.vertexshaderart.com/art/zd2E5vCZduc5JeoFz?format=json"); const data = await req.json(); ``` Example: https://jsfiddle.net/greggman/yaezcxp0/ As for running them the...

It sounds like you missed my point entirely. Maybe I suck at making my point. I totally agree promises are awesome and handle things way better than callbacks. My point...

I saw a [great talk by a harvard professor](https://www.youtube.com/watch?v=rvw68sLlfF8&list=PL4C792D55DC5318AE&index=118). Basically he said after teaching for many years and with lots of data to prove his beliefs were wrong he realized...

I'm going to throw out a 3rd option, unaware of what came up before. What if you had to explicitly release the texture? ``` const tex = context.getCurrentTexture(); ... context.releaseCurrentTexture(tex);...

Let me add, I don't know what the use cases are but, emscripten has asyncify and apparently wasm is adding a lower overhead way to implement it. I can certainly...

I think I'm confused ``` requestAnimationFrame(() => { getCurrentTexture() // µtasklist: [expire] expireCount = 1 // do stuff with texture queueMicrotask(function foo() { getCurrentTexture(); // do stuff with texture });...

> Some good error messaging in the case of using an expired texture would help significantly, I think. I'm probably forgetting part of the spec but what does this mean?...

> I think Promises are dangerous / difficult to use correctly in rendering code I don't think anyone is suggesting using promises in rendering code > It would be nice...

Is pending forever problematic with GC/cleanup? If I've closed over a bunch of stuff and my promise is never fulfilled. Example: ``` { const buf = new Float32Array(1000000); await someFunctionThatNeverResolvesNorRejects();...