It’s still pretty buggy from all reports, but maybe a sign that Deckard is actually coming.

My experience is that WiVRn is the best option at the moment since async reprojection properly works (unlike ALVR) but there is less compatibility because you have to rely on xrizer/opencomposite to play OpenVR games, which is most of them. xrizer is rapidly improving however, and already supports many more games than it did even 6 months ago.

Not my code to be clear. Maister also recently got FSR4 working on Linux, among many other contributions.

WiVRn is for VR, and I doubt it has any support for non-VR applications. It’s FOSS of course so maybe it could be adapter for that use case, but it’s probably better to integrate it into the likes of Sunshine/Moonlight.

The algorithm and code were only released a couple of months ago so it’s very early days.

It’s best with dual AMD GPUs, and maybe Intel. YMMV once you throw Nvidia into the mix.

I just think the user should be the one to decide whether they enable it or not. Pre-built PCs and motherboards can enable it by default, but it should be simple to bypass (and it usually is) and no company should be demanding or requiring people enable it.

The same applies for TPM2, which is also useful but shouldn’t be a requirement. If nothing else because of the E-waste this can cause by requiring PCs to support it. And most new PCs will end up enabling it in the long run anyway, so there is no need to force the issue.

Looks like it’s available in desktop mode too, so will work anywhere on Linux at the least.

They might mean exclusives, of which none of those apply. But I personally don’t think exclusives are a good thing anyway.

You’re not incorrect, but time has shown that some proportion of society will always act this way. And as much as it feels rational to shit on these people, a large number of people being victimised for their laziness and stupidity has flow on effects to broader society.

SearXNG also supports this with the same syntax, and can call fallback to using DDG bangs with two ‘!’ And you can make your own custom bangs if you’re self-hosting, if you’re technically inclined.

I just overuse parantheses instead, as you noted. You know you’re rambling when you have several layers of them, like I’m writing a conversation in Lisp.

Having a web UI is useful even if you’re not using the extra tools. Not mandatory of course, but nice.

I should probably add that some of this work is on RDNA3 FSR4 support, which isn’t even supported on Windows. It’s not amazingly fast, but it’s now faster than native and that might be enough to make it worth it (especially in the cases where it improves image quality due to poor TAA implementations).