Guix System is wildly different
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
I see lots of people recommending immutable distros to new users as if they are able to debug the inevitable breakages that occur or difficulty installing external programs.
This goes right with recommending Mint for gaming where Wayland is experimental and everything else is behind by several versions.
I'd say Mint is fine for gaming, as long as your hardware is supported. I'm using it with an Nvidia GPU on X11 and I can play all the games I want to play (Steam is Steam after all). My main gripe is that multi-monitor VRR doesn't work on X11, but it hasn't pushed me to another distro just yet...
For people/beginners that mostly want to game on a computer, I'd say that actually something "immutable" like Bazzite might be one of the best options.
Is Wayland better for gaming than X?
I've had multiple instances where games performed better on Wayland than on x.
For basic gaming the experience should be at the very least about equal for all GPU vendors right now. If you want anything fancy beyond that, like HDR or properly paced and multi-monitor VRR then Wayland is the only way to even have a chance of it working.
I've certainly found so. X11 is on life support at this point.
Time to use X12, boys
Yeah this I don't understand. I do use immutable distros and quite like them(Bazzite/Aurora/Kinoite) but I would never recommend them to a new user to Linux. They just work too differently than most other distros so like 90% of the documentation you might find for other programs is pretty much useless. Like if you look up some piece of software and it says use your package manager to install, then what? It's usually easy enough to solve if you read the distro's docs and use their recommended approach(flatpak, brew, AppImage etc) but that's already probably way too advanced for someone new too Linux.
I think half the reason immutable distros started being recommended to people is the fallout after LTT's Linux challenge. I noticed some people presenting immutable distros as the solution to prevent things like accidentally removing the desktop.
Some use an A/B system like Android. Others use more complex systems with image trees.
Package managers differ and also ways you can customize the images before/after downloading.
uBlue for example is heavily based on cloud technology and make building custom images with additional packages very easy.
BlendOS downloads packages and builds an image locally, making it easier to customize.
Others I haven't looked at as close, but I'm sure there are plenty of differences
That's the problem
Why do I need someone on Lemmy to tell me this when they have a whole 10 or so page website that could just as well detail this instead of the usual βHey, your keyboard works on this distroβ?
I suppose most of the website is about the difference from traditional distros rather than the difference from other immutables. Still, maybe you have a point. Go and submit a pull request to some of those websites! Write a good website inclusion in a feedback form! Join a team and help them out!
NixOS is the new βI use arch btw.β
Well, it is pretty nice ..
I use both, btw.
Okay, I get what an immutable distro is. I get it's advantages in security/safety. But can someone please explain why this matters? Like, how much safer is this really? I don't understand the cost/benefit ratio of having an immutable core, especially since compromising the core will probably require fully compromising one or more privileged processes first, at which point it would be game over for a mutable distro as well.
I think the biggest advantage for my use case is the no fuzz aspect. In the rare case something goes wrong I can reboot and select the previous version that worked without a problem. Also the ease of mind knowing I can't really fuck up my machine, as the important parts are immutable. Other than that I enjoy having everything gaming related already configured correctly as I use bazzite - but that's probably also true for non immutable gaming oriented distros.
Honestly, that's the same thing I got with BTRFS+snapper. It creates a snapshot before and after any Package installation. In case anything goes wrong I can just go back to a previous snapshot. And on top of that I can easily install native packages and don't lose any disk space to multiple partitions.
I've come to despise immutable operating systems since first encountering them in Android.
Precisely this is what I was about to comment, Thanks. Let me add that I'm using uBlue KDE flavor (Aurora) and don't get me wrong, I love it... but for many reasons I'd rather not be using an immutable distro. As a personal decision. I prefer the Snapper approach, it gives you the benefit without any of the 'costs'. But that's how I see the 'other differences'. To me, an experienced user and programmer, these 'features' are drawbacks. Immutable distros are quite good for non-power users (or whatever we may call them). Anyone without enough experience to understand the output of env | grep PATH
(to put it in some random terms). If you want to fiddle with your system, customize the shell, etc... some simple stuff that made me fall in love with Linux might be just too difficult in an immutable system... at least this was my experience as a +10 year Linux user. Just adding ZSH to the distro is somewhat difficult enough, so the distro mantainers added a 'just recipe' (which is just a Makefile, see uBlue ujust docs) to do the stuff you would consider normal if you had any CLI experience; so stuff like tweaking your system (e.g. in the past I've used arch btw) will now be alienated from usual sources like simple online documentation... But I had to try this to get to know it. So, all in all, I think these immutable distros are great for someone who just starts on Linux or programming, and forces them to keep a clean home directory, nothing crazy like conda, pip install, pipx, etc. which I've learn as a dev to use; and have full knowledge of what they do with my env. Forced me to use devcontainer, cool... I guess... So, that's the "safety" that I got from an immutable system, just being forced to keeping it tidy. Not bad, specially for a rolling distro like Fedora (the base for universal blue/ aurora.)
Great points, but I'm on the opposite side while being in a similar user group. I never used Arch, but I used Gentoo for a few years and did LFS a couple times. Now I'm using Aurora/Bazzite on my workstations. I hack around on my machines a lot but sometimes I just like stuff that works too. When I need to get some development done, I don't want to run into the weird bit of configuration left over from some previous project. I like that it pushes users towards encapsulation mechanisms like flatpaks and devcontainers. It keeps the core cleaner and more stable. The tradeoffs of having to bake extra packages into a container somewhere usually aren't too bad.
SUSE Micro uses btrfs + snapper to make read-only snapshots for it to be immutable. So, yes it's very nearly the same.
Finally! Thank you. Makes lots of sense. I've fucked up at least two systems in my life by messing with drivers/settings when I didn't know what I was doing. That would have certainly helped. I'll have to check it bazzite. I game too through Steam/Proton and it's not exactly a 100% match in terms of performance when compared to Windows.
Itβs mostly useful for stability in appliances and reproducibility in large scale deployments.
IMO, I donβt think immutability makes sense for desktop use. The whole point of a desktop is to make it personalized.
You can do tons of personalization on immutable distros. It just doesn't work the way you're used to. I use Aurora and it's an excellent tinkerer's OS.
Nix os is on the fence tho. It is immutable, but got hot reload so...
It's not just debatable, it's beside the point. NixOS is declarative, trivially reproducible and natively container-ready, that's what makes it so great.
Until you realise that you need to learn a whole programming language to run one executable outside of the package repos
I do respect nix, but it ain't for me
Iβd rather have YAML than the mindfuck of a language nix uses
[ This program prints "Hello World!" and a newline to the screen; its
length is 106 active command characters. [It is not the shortest.]
This loop is an "initial comment loop", a simple way of adding a comment
to a BF program such that you don't have to worry about any command
characters. Any ".", ",", "+", "-", "<" and ">" characters are simply
ignored, the "[" and "]" characters just have to be balanced. This
loop and the commands it contains are ignored because the current cell
defaults to a value of 0; the 0 value causes this loop to be skipped.
]
++++++++ Set Cell #0 to 8
[
>++++ Add 4 to Cell #1; this will always set Cell #1 to 4
[ as the cell will be cleared by the loop
>++ Add 2 to Cell #2
>+++ Add 3 to Cell #3
>+++ Add 3 to Cell #4
>+ Add 1 to Cell #5
<<<<- Decrement the loop counter in Cell #1
] Loop until Cell #1 is zero; number of iterations is 4
>+ Add 1 to Cell #2
>+ Add 1 to Cell #3
>- Subtract 1 from Cell #4
>>+ Add 1 to Cell #6
[<] Move back to the first zero cell you find; this will
be Cell #1 which was cleared by the previous loop
<- Decrement the loop Counter in Cell #0
] Loop until Cell #0 is zero; number of iterations is 8
The result of this is:
Cell noΒ : 0 1 2 3 4 5 6
Contents: 0 0 72 104 88 32 8
PointerΒ : ^
>>. Cell #2 has value 72 which is 'H'
>---. Subtract 3 from Cell #3 to get 101 which is 'e'
+++++++..+++. Likewise for 'llo' from Cell #3
>>. Cell #5 is 32 for the space
<-. Subtract 1 from Cell #4 for 87 to give a 'W'
<. Cell #3 was set to 'o' from the end of 'Hello'
+++.------.--------. Cell #3 for 'rl' and 'd'
>>+. Add 1 to Cell #5 gives us an exclamation point
>++. And finally a newline from Cell #6
I love writing yaml as a nix expression. That shit locks my flake.
Just 'steam-run' that shit. (It creates a regular linux-like environment without manually setting the LD path)
I use it to run random git repos.
Man doesnt even know distrobox exists
(Or flatpak of appimages or any other containers)
Good luck even finding something not in nixpkgs though
Good luck even finding something not in nixpkgs though
One of my favorite apps actually wasn't in nixpkgs (don't worry, I fixed that). But I was pretty surprised to learn that it wasn't there.
I'd say what it is, but I'd be doxxing myself.
You need to learn a whole programming language to install an AppImage or Flatpak?
Noob question for you: what does "trivially reproducable" mean?
Basically, I could send you my configuration file (and lock file) and you could run a single command to get a system that looks/runs identical to mine.