I agree, it is sad, but your McDonalds comparison is not at all the same situation. I do when possible try to use privacy respecting software. There’s a reason I’m on Lemmy. However, I’m using Lemmy from an Android phone. In many situations in everyday life, there is no simple way of avoiding having your data collected. My ISP and credit card companies collect and sell my usage information. I fortunately still have an older car, but when it inevitably dies, I’m gonna have to upgrade to one with an internet connection that also collects information. When my data is already being collected and sold by so many companies, I’m not going to stress myself out by worrying about adding one more, especially when the information they’d gain (my phone number and social media interests) is already plenty available from Google.

In your comparison, you act as if I’ve chosen to have this and have now given up. In reality, we’re in a world where it’s often the only option.

The correct answer is proper legislation to prevent and reduce this, because the sad truth is that the large majority of consumers never gave a shit.

Seriously, why should I give a shit about that at this point? Any information I put into this app they could easily get from Google.

a company that now owns the most talked about app online is not astro turfing on Lemmy.

That’s true, but its still not nvidia making that, so it’s a bit of a different thing. It will never support certain things like CUDA. It is really cool though and wouldve never happened without the open kernel modules.

Those things have nothing to do with containerization. They can do those things without it. Containerization exists to improve privacy and security. It can do the same thing on Linux.

Even if you trust an app, it can have vulnerabilities you are unaware of. Containerization helps limit the effects damage from a vulnerability could have. They also simplify the distribution of software, which is the primary goal of Flatpak. There are benefits for using containers for open source software, you’re just refusing to acknowledge them. Nobody is forcing you to use containerization, and I don’t care to convince you to. I just think acting like Flatpak and other container based package formats is some corporate conspiracy is silly. Flatpak is FOSS and mainly distributes FOSS.

Because it improves security and privacy, something they can advertise as a feature. There’s no negative for them to implement, it’s their phone, they can already collect all the data they want. It still prevents other apps from accessing data they shouldn’t.

Why do you think phone makers push it? What possible malicious reason do you think proprietary software makers have to push containerization and sandboxing? What do they gain?

Flatpak is completely open source software and any proprietary software in it has a large warning about how it’s proprietary. I don’t know why you think proprietary software vendors are pushing these. Ublue, NixOS, and Fedora Silverblue are all community run, not being pushed by some malicious group pushing proprietary software.

Why companies even have anything to gain from their proprietary software being in a container? All that would do is make data collection more difficult.

I don’t really know what you’re saying. Most software is distributed as binaries, that doesn’t make them inherently untrustworthy, you just need to have trust in whoever is distributing it. It’s trivial to look at the build process of a flatpak and verify that it is legitimate. Just because the binary isn’t being built from source by every user doesn’t make it insecure.

Yep, Nvidia has never been hostile towards Linux, they benefit from supporting it. They just don’t care to support the desktop that much, and frankly neither do AMD or Intel. They often take an extremely long time to fix simple bugs that only effect desktop usage. Fortunately, in their case, the drivers can be fixed by other open source contributors.

They only open sourced the kernel drivers, which just makes sense for them to do. Userspace drivers, which these attackers wanted to be open, are still very much closed. Likely had nothing to do with it.

You might be spending too much time on Lemmy if you’re still finding it lacking in content. Unless you’re referring to the amount of content in niche communities, in which case I’d agree.

You’re definitely out of date on your knowledge then. Nothing inherently insecure about any of these. Only download software you trust, just like you should be doing with any software format!

A distro can be both atomic and immutable, and they often go hand in hand.

Immutable simply means the core of a distro is read-only, meaning it cannot be modified by usual means. There are still ways to modify these files, but it works differently than in other distros.

Atomic distros are ones that update atomically. Atomic is used to describe an operation that cannot be cancelled in the middle of it, they either complete, or nothing changes. This means you can’t break things by cancelling an update midway through. Atomic distros also often come with the ability to rollback to the previous build of the system.

Immutable ≠ atomic, but they generally come as a package deal. Bazzite, Silverblue, and all those other distro’s that call themselves atomic are also immutable. An atomic distro is just one with atomic updates, and an immutable distro is any distro with a read-only core.

These distro’s have started mainly calling themselves atomic because they agree that immutable is a poor description that generally confuses users.

Linux isn’t about choice, it’s about freedom. Distro’s don’t owe you the choices you want, because the devs have the freedom to make what they want. You also have the freedom to modify them or make whatever distro you want.

Don’t know why this would be downvoted. Atomic distro’s are a tinkerers paradise, as all of it can be done fearlessly. I can make stupid changes to configurations that I don’t understand on NixOS, then when things break, simply revert the git commit and rebuild. (Or reboot to the last build if I broke it bad enough).

I don’t have any pics cause I’m not currently near my computer that runs bazzite.

If you’re mainly using GUI apps you’ll probably just be installing everything through flatpak, which you can use via the Discover store that comes with KDE Plasma. CLI apps are installed using homebrew.

The docs might give you some insight on using it: https://docs.bazzite.gg/

Since it’s immutable, you’ll probably not be using DNF much.

NixOS likely only refused to run it because you weren’t running it in the Nix way. That’s not a jab or anything, Nix has a huge learning curve and requires doing a lot differently. You’re supposed to use devshells whenever doing development. If you want something to just work, you use a container.

Whatever issue you ran into most likely had nothing to do with NixOS being immutable, and was probably caused by the non standard filesystem hierarchy, which prevents random dynamically linked binaries from running.

I’ve never heard of flatpak and immutability being obstacles to developers, in fact I generally hear the opposite. Bluefin is primarily targeted at developers, and some apps, like Bottles, will only officially support the flatpak distribution because of the simplicity and benefits it brings over standard distro packaging.

That doesn’t make it not immutable. /bin is not a critical directory in NixOS, only the contents of /nix are, which are immutable. /bin isn’t even part of your path by default.