sometimes is an understatement there. It took me like a decade to get that shit right. Graphics in general seems to suffer from bad explanations repeated everywhere. We need more authoritative textbooks.
Modern APIs make synchronization and resource management a lot more complex. Used correctly they result in better performance; used incorrectly...
That being said, "nowadays" most studios just throw shit at UE5 and get it over with. It's obvious from how terrible many games run that they don't have a rendering engineer on the payroll.
There is no AI use here. I'm somewhat offended by the suggestion even though I have no relation to the author. Bartosz has been shredding for a long time now. His javascript is also unminified and perfectly readable, making it a great reference for study despite not being advertised on his pages. The animations are all hand-made. The guy is cooking. To suggest that any of it is AI is an utter blasphemy. AI is for noobs, grifters, and low-effort content farmers and Bartosz isn't any of those things.
Probably people who don't register the name. Your comment adds nothing and is the kind that always ends on the bottom of the thread, so you shouldn't take it personally.
Great website, though. I'm fixing my time step all day.
And what does that have to do with the guy leaning right? He runs a VPN. If you care about privacy, that should be sufficient to support it, his other opinions aside.
I think it's because it's what every tutorial does, and people just copy-paste that template without giving it too much thought. Just need to dig through the API a little.
At least with SDL3, you don't even need the renderer or the texture anymore. SDL_GetWindowSurface to get the surface and SDL_UpdateWindowSurface to present. That's the more software-graphics you can get from my understanding of the library. SDL still does the double-buffering for you.
The noise from this technique would come from moving lights and world-space disocclusions. Lights don't move erratically in most scenes, objects maybe. But even then, this handles diffuse illumination only, which by its nature has low frequency noise. You won't get noise by shaking the camera violently like in an FPS, for example, which you would from modern ray/path-traced pipelines and I assume is what you're complaining about. So on the list of temporal techniques, this one is probably the most graceful to the noise/lag trade-off.
"Crisp, noise-free, instant graphics" that were also incorrect and did not communicate mood and depth the way GI does. I see no reason to go back.