I use keyd for software remapping now, and I like it a lot more than xkb’s esoteric options. It has functionality for layers like layer:C, where any “passthrough” input will have the defined modifier (or combo like C-S-M), but you can define whatever other bindings inside.

Long story short, I’ve used it to remap caps, control, shift (with a custom shift layer for some symbols), and meta, with overloads, double tap/hold into layers, oneshots, timeouts, and all sorts of (surprisingly fluid) nonsense. It’s so much easier than wading through xkb options for me.

To sidestep the question slightly less, I always got rid of capslock altogether instead of swapping. That still leaves true escape to be hit accidentally, but I think there should be an option to change escape too?

Edit: what I always used was

# make CapsLock behave like Ctrl:
setxkbmap -option ctrl:nocaps

# make short-pressed Ctrl behave like Escape:
xcape -e 'Control_L=Escape'

from here

Honestly I thought it was standard for modern electronics, or cells themselves, to internally consider 80% as full

Generally I agree. It feels kind of shoehorned in when desktop is your goal, like more of an afterthought or side effect of the overall focus.

The main thing I hang on to is the code-specified configuration. I never got into managing dotfiles with arch, but that could be a better solution for many people. Especially along with btrfs, numerous containerization options, and whatnot.

I went from Arch to NixOS, so I can offer a bit there.

You definitely won’t want to rely on it until you know a good amount and get comfortable. Things can be made to work, but knowing how to get it done is the main thing most of the time.

Regarding package availability, it’s just a matter of a few oddly esoteric incantations and version controlled code, usually. Binaries are another story but still possible, and python is a special case of that.

It has been an annoyance for me, but I’ve also learned a lot by getting things to work. If you use any niche python stuff you’re bound to run into something. A bunch is already packaged and works fine, though. Either way there’s a bit of extra nuance, which is more to learn.

You don’t have to start with NixOS and can feel it out using nix on any distro. It can be hard to tell if someone will vibe with it. All that said, it could be more than you’re looking to get into, but you can ease into it if you’re interested.

To be fair, it’s software specifically designed to run digital backups of what’s supposed to be personally owned media. It just so happens that it’s very easy to obtain a copy otherwise, but there’s nothing inherently illegal about it or the games.

Strong arming independent projects, and individual developers especially, that are very careful to not endorse that, effectively holding them accountable for others, is morally questionable at best.

I’m still on bemenu since I used dmenu with dwm on X. I should probably check the others out.

Well there ya go! I figured it was still too niche.

No distro is really based on a window manager or desktop environment. Some provide defaults and premade configs. I kind of doubt any include hyprland as an option at installation, but, Wayland compatibility notwithstanding, there’s nothing stopping you from throwing hyprland on whatever you would like. The best approach is to take a Wayland-ready setup, like Leaflet suggests, and just install hyprland.

Don’t you dare talk about Navi like that!

It’s gotta have a massive battery unless it’s running AAA games for like 15 minutes…

I went from Arch to NixOS and I’ve been loving it. I also had all the time on the world to dive in with several machines to fall back to.

There are a lot of layers to wade through especially when you need a specific tool like your UE5 case. As others are saying, there are ways to make everything work, nix or non-nix, it’s just more to work through after getting the bases covered.

Anecdotally, I had little trouble getting set up on my MSI laptop with an RTX2070, Primus and all. That was after learning the ropes on a Ryzen IdeaPad.

Rambling aside, I would definitely make sure to start in a non-mission-critical way, but do jump right in if you’re comfortable. Maybe if you can stomach the Asus a bit longer, or get the Framework set up and play around with the Asus. And ask plenty of questions! I know I’m not alone in jumping in on nix questions any way I can :)

Naughties is British/Australian for aughts or '00-'09. And then I think boomer refers to “boomer shooter”? Or just the fact that zoomers call (older) millennials boomers.

My first reaction was also to make fun, but it kinda seems neat and it’s different, which I welcome. Really hope there’s plans to support one strip across monitors cause that would be kind of dope to look at.

Edit: also I’ve had a pretty easy time with a 2070 running Wayland once the drivers and wm are right. I did manage to mess up my old nixos generations trying to get started and changing things around lmao. Landed on hyprland, and it’s smooth.

I learned a ton from this, it’s kind of “The Book” I guess. For OP, there’s a pretty massive series of blog posts I fumbled along with too, https://ianthehenry.com/posts/how-to-learn-nix/introduction/ though it’s a couple years old.

Don’t know whether to call it getting steamed or getting decked

Proton on Linux is annoying to say the least. I’ve got it mostly working on my distro and without a DE. Have you checked the protovnpvn_reconnector service, assuming you’re on systemd? It’s kind of odd that it just slows to a crawl but maintains connection.