FYI, setting `NvOptimusEnablement` and `AmdPowerXpressRequestHighPerformance` have been the canonical way on Windows, `__NV_PRIME_RENDER_OFFLOAD` + `__GLX_VENDOR_LIBRARY_NAME` on Linux. Though not an OpenGL feature per se, as you mentioned.
Same comment, same wording was had when going from H.264/AVC to H.265/HEVC and again to AV1. Across the board it's 30% better Size vs Quality and with an X amount increase in compute required to encode and decode.
Each time these standards were put into ink, they were years from being practical.
Self hosted gitea for many years with ~25 devs.
Yes, it's essentially a FOSS carbon copy of GitHub. CI/CD is also intercompatible, uses the same syntax and pulls the original GitHub Actions packages.
Now with the Forgejo split, I would prefer Forgejo, as it has way more steam behind it with Codeberg and Blender as the big use-cases.
So So useful <3
Stabilization = you have to zoom-in, loss of FOV. Depending on Action Cam and undistortion parameters, this can be different, sometimes too little, sometimes too much. Gyroflow allows you to dial it in. Lot's Stabilization in a particularly shaky spot and widest FOV everywhere else, smoothed between to be unnoticeable.
> But a compiler is deterministic — same input, same output. An LLM isn't.
Temperature 0 determinism is subject to active research. NVIDIA tried but failed so far, DeepSeek V4 seems to have done it. I hope judges won't be swayed by this an AI generated code will classified as uncopyrightable, just like Images are.
You are of course right. It's just that Modules inherently put a lot of responsibility on the build system. Among those, but not limited to: a "module registry" wasn't standardized and is in the hands of the build system.
Systems like ninja needs to know modules, which took time and then a stack further up systems like CMake needed to know modules, which took time. That's my answer to the parent "why are there so few modules projects". Because it took time for the ecosystem to catch up.
It's the fault of built systems.
CMake still doesn't support `import std` officially and undocumented things are done in the ecosystem [1]
But once it works and you setup the new stuff, having started a new CPP26 Project with modules now, it's kinda awesome. I'm certainly never going back. The big compilers are also retroactively adding `import std` to CPP20, so support is widening.
Also it's missing the point of the parent: it's about concepts and ideas merely being remixed. Similar to how many memes there are around this topic like "create a fresh new character design of a fast hedgehog" and the out is just a copy of sonic.[1]
That's what the parent is on about, if it requires new creativity not found by deriving from the learned corpus, then LLMs can't do it. Terrence Tao had similar thoughts in a recent Podcast.
Same here (10s to 1s). The main reason for this is rolldown [1]. Already had it installed months ago, before it got merged into vite proper. Really awesome stuff.
> and it won't work without Steam running. Such a disappointment
I assume it will be like Steam Controller 1: Given no Steam and no special driver, the Controller is a Mouse + Keyboard, also referred to as "lizard mode".
I am also anti-DRM, but I don't think this can be solved easily. Consider the Dual Shock 2: Either it's explicitly supported or requires a custom diver to emulate into XInput or DirectInput. Even using XInput directly is cross platform a driver nightmare.
Valve has done good work I think with their libSDL based Steam Overlay, becoming a kind of universal Input equalizer, going so far as to patch their games with updated tutorial input prompts based on controller like Dual Shock 2 vs XBox Controllers.
A firmware level solution is not really realistic at this point. Controller Manufacturer 8BitDo went this approach, with many device restart firmware modes per target platform. It's just not a good user experience.
XUASTC was just released, allowing for all ASTC Block sizes to be used on the web, once support lands in the big web 3D libraries like Three.js [1].
To me, this is huge. Relying on pre-calculated lighting when building stuff like [2], I constantly fight for VRAM, as older iPhones have very strict limits. XUASTC brings the all the remaining modern GPU compression schemes to the web in a standardized manner.
I’m a bird , not a fruit. PLS don’t eat me :S