Oftentimes it’s someone creating and maintaining a piece of software or tooling for themselves and their own benefit. They just happen to be nice and forward thinking enough to share it.

In my experience, Seagate exos are only “loud/clicky” when under HEAVY write loads. Mostly they’re pretty quiet with a very low drone at worst. In any decent case it’ll be pretty negligible. With headphones on doubly so.

Yeah, logging in pulled across everything, as far as I can tell. Subscriptions included!

Grayjay on Android has been working damn near flawlessly for me. No clue if the parent company is to be trusted at this point or not- but I cannot argue with the results.

Absolutely this. Relatively quick and clean, no messing with installation or reconfiguration. That is, assuming your data isn’t completely corrupted and the old drive doesn’t just outright fail during transfer… But if that happens you were screwed to begin with.

Dark thick beer can also work in place of cocoa, in my experience.

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…

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.

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.

There’s an old article on the Arch wiki I used to use HERE. For simplicity I’d just always use section 2.2. Hasn’t ever steered me wrong, but I’m also under no illusions that no digital data is sacred. And if it IS sacred, then it’s already backed up under the 3-2-1 approach. Just make sure you know which device is which so you don’t mix up “if” and “of”. There’s probably significantly more user friendly ways of doing it, but I guess I’m old now so I’m stuck in my ways.

Get a same sized drive (or larger) and just dd it? I used to do that all the time, even to Windows installs, if I knew a drive was starting to become unreliable. I’d advise mounting the original/donor drive as read-only to mitigate any potential data losses while transferring. But dd makes a perfect bit for bit copy of any partitions, drives, etc that you feed it. Just don’t get the inputs/outputs backwards! And always remember: dd stands for “disk destroyer” because if you get it wrong, bye-bye data.

Self hosting Mealie could be a great option to take things into your own hands.

To be more clear I was more focused on the not wanting a car that needs software updates part of the argument, less so the means of delivery. Obviously, having an always on connection absolutely sucks and I’d personally be super down with just pushing an update via a USB drive or whatever like you can a BIOS update. But a lot of manufacturers have it set up so that you have to either pay a dealership to plug in the USB for some arbitrary reason, or demand the always on connection to do it. In a utopia of software development where there are no critical bugs, we would all prefer a car that doesn’t need updates. I didn’t mean to imply that I was arguing in favor of remote connection by manufacturers, and it’s absolutely my bad in not wording it properly.

On the flip side: if a car stereo has a known firmware issue causing problems with say Bluetooth connection, I DO want the manufacturer to actually provide an easy means of fixing/updating the borked software. Better that the system was properly tested and feature complete to begin with- but I’m not delusional enough to believe we can truly have nice things.