hrydgard

More than half the article is AI slop. Sad.

This is just AI slop explaining the very basics of what a pixel/fragment shader is. The usecase is not particularly useful. Doesn't belong on HN.

Got taught this one in Sweden in the early 90s. Not too surprising though, as much of the Swedish school system used to be modeled on DDR...

Maybe a cache coherency issue, where data written by the CPU is not visible to the GPU, without some kind of explicit cache line invalidation, maybe on both sides? Caveat, I don't know much about the memory system on the XBox but this is a typical issue with homebrew code on consoles.

Or you just go ahead and forget that big endian ever existed. It's not coming back.

Well, it is what is done on several tiler architectures, and it generally works just fine. Normally your computations of the position aren't really intertwined with the computation of the other outputs, so dead code elimination does a good job.

BC1-3 are like that, but BC7 is far, far more complex. The search space is huge.

It works just fine and is natively ARM, since a year or so.

What about implementations? libpng seems pretty dead, 1.7 has been in development forever but 1.6 is still considered the stable version. Is there a current "canonical" png C/C++ library?

Parody account

Great stuff!

Small UX thing: Make it so you can just click a word to fill in the next empty spot, instead of having to drag, similar to when building sentences in Duolingo. Especially when not on a touchscreen, having to drag is pretty painful and reduces accessibility.

Function calls are very fast (unless there's really a lot of parameter copying/saving-to-stack) and if you can re-use a chunk of code from multiple places, you'll reduce pressure on the instruction cache. Inlining is not always ideal.