Drathro

Compatibility is unlikely to be very different. The key is immutability (easy to update, hard to brick your system) and some baked in nice to haves for gaming like some specific drivers/patches and controller support out of the box.

Cheaper than Spotify for the number of users it gives you (at least where I live) and the app itself has functioned significantly better than Spotify's has in my experience so far while not depriving me of any of the artists and albums I listen to regularly. Early on in its life it was big time selling snake oil, but at this point it's just a solid alternative to Spotify and YouTube music which have both, frankly, gotten "too big to fail" and have begun enshittification because of it. Man we need more competition...

Just tracking trended data in general would be sufficient to defeat a LARGE number of common cheats. One of the very few use cases "AI" might actually work for in a positive way. But that puts the burden on the developers and server hosters, and it's much easier to just burden the players directly instead.

My old Nexus 5 was my first smartphone and probably still holds the top spot for price, performance and usability (at the time) of any phone I've owned. My current Pixel 6 is somewhat close- but there was just something SO solid and magical about the old Nexus 5.

If you're gaming you might as well just jump on Bazzite if you're already interested in Kinoite. Very similar base, but Bazzite has some extras Kinoite doesn't and it makes a transition into an immutable distro easier.

It's in the appendices. It tells us the authentic Westron names of all the main Hobbits we follow.

If we wanna be pedantic (and I usually do), Pippin’s Real Name is Razanur.

AMD with ray tracing isn't great. Not as bad as it used to be, but pretty lackluster overall compared to Nvidia (and to a lesser extent Intel's GPU offerings). Linux ray tracing via Proton is also not as optimized at present, so that can take something "passable" in windows and make it unplayable on an AMD card in Linux. If you get something overkill for the resolution you're playing at that can somewhat make up the difference.

If you're doing 1080p the 6600 is pretty solid. Or 7600, really. It CAN do higher resolutions, but then you'd need to start doing FSR scaling or drop settings to keep things smooth/consistent.

I'm just here to say Bazzite all the way. No clue what that poster meant by breaking issues or problems with rollback... Bazzite is literally designed to be the antithesis of both. The ONLY time I've had a problem with it was rebasing my laptop between Silverblue and Bazzite. Technically allowed, but I wouldn't advise it as that did cause me stability problems. I'd blame Silverblue more than Bazzite in that case, however. A clean Bazzite install has been solid ever since.

You seem to be arguing it's all about the implementation of the phoning home itself- I'm arguing that running the entire executable/binary through a virtual environment likely has far more drastic performance implications than a phone home, regardless of frequency. It probably IS mostly an implementation problem, but I'm more inclined to believe that the implementation of the Denuvo virtual environment is at fault, not just a server call and response delay. **EDIT: Apologies, forgot to include a link- see HERE. Looks like a substantial/measurable difference. Not massive, as measured here, but certainly enough that if your hardware is just barely able to run a game it could easily make or break the entire experience.

Regarding performance implications: I believe Denuvo DRM runs through a type of virtual machine environment. While this theoretically should be relatively transparent, there are definitely documented instances of it negatively impacting performance, sometimes severely. Maybe the VM it runs in is just bad with certain instructions/calls on certain CPU's or api's, hard to tell for sure. But it's not nothing.