Meanwhile if you want to *really* optimize your performance, you should be prepared to rewrite your opaque rendering pipeline from forward+ to deferred 5 months before release, while reinventing variable rate shading for compute and hiding all the ugly artifacts. [idSoftware2025]
*wheezes respectfully back in your direction*
New Use.GPU release (0.18) with:
- order-independent transparency (WBOIT)
- improved dolly zoom to full orthographic, with support for SSAO and other post-fx
- rewritten quad-tree map tile renderer with arc labels
Docs and demos at: usegpu.live
Just seems like dream logic to me. The illusion of consistency is maintained only from frame to frame.
❤️
Live also has a multiyoink per your terminology, yoinking into a map of lists.
Use.GPU now has this sweet black hole raytracer:
usegpu.live/demo/rtt/bla...
Use.GPU 0.15 is out!
Highlights:
- Shaded lines and point clouds
- Narrow and wide (>90º) spot lights with hemispherical shadow maps
- Improved GLTF `.bin` loader for packed/inline textures
Also finally rendered a Sponza atrium.
Demos:
usegpu.live/demo/plot/tu...
Docs:
usegpu.live
Releasing "Stable Fiddusion", a frequency-space 2D/3D/STBN blue noise generator. WebGPU implementation goes brrrr.
acko.net/blog/stable-...
Weebs always get weird when you point this out
When you move the portals, what happens?
This wasn't generated by AI, a person drew this ages ago and then someone cropped it and added the caption.
I'm just peeking in here while looking for interesting accounts to follow, so I just want to say:
Your inability to accurately model the beliefs of your opponents will be your undoing. Keep it up.
New post on the math behind Use.GPUs secret subpixel SDF sauce.
With zoomable diagrams if you're on a WebGPU capable browser.
https://acko.net/blog/subpixel-distance-transform/
It used to be "talk is silver, code is gold" except now it's like a freemium game where silver is the worthless dopamine drip and gold just costs money.
tpot, an illustrated guide
An interactive code/data walkthrough of Live, the incremental effect run-time behind Use.GPU:
https://acko.net/blog/do-it-live/
The entire purpose of organizing code is to produce a structure for people. The compiler doesn't care, it would be happy with 100 files in 1 directory.
The reason to keep it at an ideal size of ~7 files per module is human short term memory.
Bad:
- prettier / autofmt / etc
- IDE inserts imports for you
- copilot / chatgpt
If I ever get around to hiring people, these will be fireable offenses
>we prefer to delegate stuff like that to tools
>why has our codebase grown so messy can you help us fix that
same people
And whether different URL implies different back/forward state or not. You know exactly what you want in each case, but this is not super obvious unless you very carefully think about it.
I will eventually write my "here's what you should've been taught about how to structure your react codebase"... but not right now because I don't need more work
Hey @pfrazee.com if you need someone who knows how to use react so your codebase doesn't become unmanageable after a year, hit me up.
Tbf I don't really blame bsky for this, the web is complete trash if you're coloring outside the lines.
I was wondering if anyone other than Twitter could make a half decent infinite scroller web app but based on how much this app spazzes out when you press Back the answer so far is no.
Same on the first. Most of my habits around cleaning are learned, and result from the fact that a clean house is cognitively much less taxing and hence more pleasant.
OTOH in any decent city you can find a bar open till like 8am
It's still considered adventurous to move away from "under the church tower" you were born at here. Different timezones are crazy future tech.
Before you can show them the aspirin, the head ache from their existing code base has to be untenable.
Glibly, 10x engineers write 10x less code. So it's very demotivating and ego-threatening to show dev who worked for days to get the bugs out of their pile of spaghetti that you can do all the same stuff with a single meat ball.
The secret to doing magic with code is not genius tier effort but just writing as little of it as possible. I find this is impossible to teach. You have to feel it in your bones.
