I assume it’s a different system since it works on Wayland, but idk

Honestly, they just shouldn’t have added support. GNOMEs been causing problems for basically everyone else for a long time. If they want to do their own thing, that’s fine, but we shouldn’t but everyone else shouldn’t have to do extra work to accommodate them.

People learn about different things at different times. If we care about promoting privacy we should be accomodating and not hostile about that.

In addition to everythong everyone has said, one major thing that people often don’t think about privacy is how it relates to enshittification.

Modern software services try to optimize everything to make as much money as possible. Everything is a/b tested, and whatever increases some arbitrary metric is what gets released.

They do this by tracking a ton of metrics about how you interact with everything. I know where I work we collect data about every time you click on anything, how long you hover over buttons, etc.

The only other (not absolutely tiny) one I’m aware of is brave, but it has its own issues

Yeah, recently I’ve run into 1 game I’ve wanted to play that I just couldn’t (Valorant so probably a better outcome lol) and maybe 2 that had any sort of issue.

If you’re mainly into competitive games it’s still rough, but otherwise it’s honestly smoother than my friends on Windows often.

Yeah, imo the problems solved by using snaps for core system stuff are better solved with immutable distros, and I see very little reason to use snaps for anything else.

Yeah, sorry couldn’t resist.

snaps are very similar to flatpaks and, honestly, is technically better in a lot of ways.

Snap can be used for basically an entire system, while flatpak is limited to graphical apps. (Ubuntu core is built basically entirely off snaps.)

Snap is controlled by canonical, and the backend for the snap repo is entirely closed source. I’ve heard snaps are also easier for developers to work with, but I haven’t experienced that side of them.

Snaps automatically update by default where flatpaks don’t.

Snaps also get treated as loopback devices when they’re installed, which bloats a lot of utilities. (And they keep a few old versions around which makes it even worse). For example, you could run lsblk and if you’re using snaps like 90% of it will be snaps you’ve installed instead of actual devices.

Flatpaks are also noticeably faster to start up, which for desktop apps matters, but wouldn’t really matter for a server that’s aiming for a lot of uptime.

The loopback device issue is the main reason I don’t use snaps. I also like flatpak being completely open, but realistically that doesn’t matter for much. There used to be an open snap store, but that shut down because nobody used it.

The easiest way to think of it is flatpaks are AppImages with a repository and snaps are flatpaks but bad.

That has benefits and detriments. Appimages contain everything they need to run, flatpak’s mostly do, but can also use runtimes that are shared between flatpaks.

All flatpaks are sandboxed, which tends to make them more secure. AppImages can be sandboxed, but many aren’t.

Flatpaks tend to integrate with the host system better, you can (kinda) theme them, their updates are handled via the flatpak repo, and they register apps with the system.

AppImages are infinitely more portable. Everything’s in one file, so you can pretty much just copy that to any system and you have the app.

Yeah, but people installing GrapheneOS probably aren’t in the vast majority of users

deleted by creator

I agree with pretty much everything they’ve said, though I’ve gotten more use out of the swappable parts. I have a desktop I use for things I need a powerful system for, but being able to swap in the GPU when traveling is great.

When I’m at home I have basically everything on USB C and the empty expansion bay.

When I travel I swap in the GPU and add an HDMI port and some USB a ports.

If you don’t have stuff set up like I do I agree it’s mostly just a reparability / upgradeability thing.

You could try flashing the recovery image and re-imaging your deck. https://help.steampowered.com/en/faqs/view/1B71-EDF2-EB6D-2BB3

I’d contact valve support if that doesn’t work, they’ve always been great whenever I’ve interacted with them.

Oh yeah, they’re free to decide, I just disagree with them! I get the decision though, and if I were on charge of a large distro, I’d probably make the same choice (until plasma is on a normal release cycle)

Yeah, like I’m all in favor of having an opinionated design, but their dominance makes their bad decisions actively harm every other de. Stuff like refusing to compromise on cross-desktop protocols

Their whole attitude towards development is similar, down to not working with other dekstops and insisting on doing things the way that works best for them regardless if it’s worse for the linux ecosystem overall.

Nah, GNOME is worse mostly because it’s the default on a ton of distros, so them having this attitude actively get’s in the way of cross-desktop development instead of just being annoying.

Yeah, KDE’s basically at the point you don’t need GNOME imo, it’s so customizable you can make it basically look/function the same as GNOME without having to put up with GNOME’s dumber decisions

My only concern with nobara is that Fedora 41’s dropping x11 support, and I’m not confident nvdia drivers will be in a good enough state to recommend to a beginner.

Yeah, I’ve heard it’s getting better, but I have an amd card, so not really sure where it’s actually at. X would probably be better for nvdia for a while, especially on pop_os, but idk what the actual state is.