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!
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!
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.
Why bother setting up a hosted DB server when you can get all of the RDBMS optimizations in an in-process service? DuckDB is pretty cool
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?
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…
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.
deleted by creator
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.