Ah yeah that looks perfect, just get WayBlue Hyprland then! That sounds like exactly what you need.
No need to mess about with user services in systemd and display manager config.
Ah yeah that looks perfect, just get WayBlue Hyprland then! That sounds like exactly what you need.
No need to mess about with user services in systemd and display manager config.
NixOS
Alternatively (speculating here), you might be able to use Nix to install Hyprland onto an existing immutable distro like Silverblue.
Nix people please chime in!
Yeah that’s the whole Enterprise LTS issue. RHEL is the same, as is Ubuntu after a literal decade of LTS support.
I am so happy that we have podman in RHEL 8. Rootless podman containers with distrobox are a godsend in these software geography dig sites that have to pass for a workshop.
I have never heard of WattOS but that sounds terrible.
It seems like antiX is a systemd-free Debian flavor.
If you want systemd, why not just use Debian? Or, if you are looking for a nice preconfigured DE/WM, any of a number of Debian/Ubuntu derivatives.
Mint for best out of the box setup, Pop!_OS for tiling, Zorin OS if you’re looking for a funky styling, any of the Ubuntu derivatives for the major DEs: Kubuntu, Xubuntu, etc.
The time between “start integrating” for an Ubuntu release and the actual Ubuntu release, is typically a full kernel release cycle IIRC. It takes months before it is actually released. Once it’s in your daily driver, it won’t be a release candidate kernel anymore.
Not supporting a newly bought modern computer out of the box is pretty bad for an OS that claims to be accessible and easy to use. So I understand the shift.
I trust their testing process is adequate to ensure stability at release.
Great post! Completely agree! I will add that for filling out PDF Forms, Okular is amazing!
chezmoi does basically that, without actually making your home dir a git repo, it just syncs it. It also supports templating and per-machine differences. Pretty cool really.
SMB is originally Windows tech. So it might not play nicely with file modes?
And since we’re on the topic, if we’re borrowing things from Android I would love to have the application sandboxing and permissions. I think they’d be a much bigger benefit – to all distros, immutable or not.
Flatpaks and Wayland should fill out this part nicely.
I’m guessing this refers to the not entirely separate groups of Nix(OS), Haskell, XMonad fans
Distro version of Firefox worked wonderfully for me on EndeavourOS (Arch repo / Wayland / Sway) and Pop!_OS 22.04 (Ubuntu base / X11 / GNOME)
Completely off topic, but: I’ve been trying Fedora (KDE spin) for a few months now, and I’m flabbergasted at how unusable the distro version (not the Flatpak) of Firefox is. I think it’s a codec issue as I’ve checked Firefox is running in wayland mode, but:
Meanwhile, the Microsoft Edge flatpak works flawlessly.
Are you using a flatpak browser too? If not, how did you get your browser to work?
I really like Fedora otherwise: up-to-date kernel and modern (very efficiently stored) packages, but properly tested with major releases, btrfs and systemd by default and commonality with RHEL is useful at work.
But these codec issues are pushing me back to Arch…
That’s what I get for not reading the full article and posting a meme response from the salty toxic Linux user stereotype. Apologies!
emulated Windows
Tell me one more time:
I um… didn’t get started yet. But a colleague demoed it to my and it’s kind of between virtual environments and containers, if you’re familiar with Python.
You write a Nix config and specify exactly which versions of which package you want to have. Reproducibility is the main selling point of Nix. Things don’t just break overnight because a dependency of a dependency of a dependency got upgraded. You can always go back to exactly what it was like before. Guaranteed. That’s pretty cool.
Ok so you got that config, then you build and activate it, and it replaces your shell. You enter the Nix shell. You still have access to all your files and directories, but your Nix config controls exactly which versions of your tools you have. gcc, npm, python, maven, whatever you use.
You can see why this makes people want to build an immutable OS.
The main drawback of Nix is that it has a bit of a learning curve. Hence why I haven’t started yet. Maybe it’s time though.
Don’t listen to him! Just start using Nix to manage dependencies and dev environments for your projects but keep your OS the same until you are really good at Nix
OpenSauce
Or, taking SUSE -> Soße -> sauce
Exactly! If you only have to edit small text files on a server once in a blue moon, nano is much less biomemory-heavy. But if you regularly write docs and code in l vim or neovim, it starts to pay off after a week or two.
I really enjoyed learning to quickly select and change entire words or lines, doing things like:
:%s/replace_this_text/with_that/g
Etc.
If you enjoy that, you will soon get to a point where you miss the motions in your regular editor and install a vim extension in VS Code and stuff, just before fully switching to neovim
Try running this:
vimtutor
If you are already aware of hjkl, skip to the part where you learn motions:
/motion
Then look up surround (ysw
is usually the command to surround a word, ys3w
the next 3 words, etc)
It’s pretty neat.
Yes, you are right.
The old stuff, now no longer supported, is:
The new stuff: