autokey

I accomplish the same thing with compose sequences, and by binding a keyboard shortcut in my desktop to call a script with wtype. It's not a cross-compositor solution though, as you'd have to manually setup binds in each of them.

I don't see much hope for this one-to-one unfortunately.

I think each of 3.8 through 3.11 were substantial, just in different ways.

Judging purely on the dependencies I see in pacman, nsxiv depends on imlib2, which pulls in a lot of libraries, while imv links to a subset of those libraries directly.

A few from Itch, Parallel Launcher from Flatpak for SM64 hacks

Also, monetization

Exact same. Sway's 1.0 release was March of 2019, and it did everything I needed.

Even playing games on my desktop, Xwayland worked fine for me.

They are becoming more essential by the day. HDR and VRR is supported by just about every graphics card for the last 5 years, and displays which support both can be found for $200 or less. Valve had a reason to add HDR support to Gamescope/Steam Deck; it is a highly requested feature.

I will agree with you on one point: Xorg is not bad code. Xorg is an awesome project, and has developed and changed to the needs of users exceedingly well for decades. But X11 itself is tech debt. The first ten years of Wayland were spent paying that debt off (while simultaneously continuing Xorg development).

If the features aren't what you need, then Wayland wasn't built to support you today. But you might find yourself in 6 years looking at a gorgeous HDR display which works out-of-the-box on your favorite Linux distro thanks to Wayland.

type -p is a shell builtin though, and one character shorter :)

Although you may prefer tool=$(command -v tool)

It's interesting, the results here are way different than the Code Golf & Coding Challenges Stack Exchange. I would never expect Haskell to be that low. But after looking at code.golf, I realize it's because I/O on CG&CC is more relaxed. Most Haskell submissions are functions which return the solution.

Sidenote: I like the CG&CC method, it's semi-competitive, semi-cooperative.

• all languages welcome
• almost all users post "Try it Online"/"Attempt This Online" links
• most users post explanations under their submissions
• often people will post solutions beginning with "port of user1234's excellent Foolang answer" when there's a clever shortcut someone finds
• or people will post their own solution with "here's a solution which doesn't use user1234's algorithm"
• or people will add comments to answers with minor improvements

IMO It's geared towards what is the best part about code golf: teaching people about algorithm design and language design.

I learned Fish by helping someone else in a chat. There's a lot of cool things, and I think it's an excellent shell. Fish is an excellent choice for a shell.

Zsh is a much more featureful language (with globbing/subscript/PE flags, native floating point arithmetic, the whole man zshmodules), which doesn't necessarily make it a better shell. But I like those features, and I find it to be a natural choice to write more complex programs which normally would be a code smell for Bash.

The plugin ecosystem for is much larger than Fish's as well.

"Always configuring" isn't what Arch requires. It requires you to be tolerant of every so often dealing with a bug or two. Currently, the Arch-packaged version of Waybar has a regression which prints fractional seconds when using %T or %S specifiers. A tad annoying, and I could fix it by switching to waybar-git, where it's been patched. But that hasn't hit my threshold of annoyance, as I bounce between Sway and KDE.

The grub issue was a bigger deal, and while I knew how to resolve it (liveboot → lsblk and fdisk -l got me all the info I needed, then cryptsetup, mount -o subvol=@, arch-chroot, grub-install) the EOS blog had a nice guide.

But the reason why I chose it? Firewalld and Pipewire by default, customizable welcome app, and pretty simple otherwise.

NixOS will probably fully convert me in a year or two, but I've greatly enjoyed my time on Endeavour.

I've done symlinks into a separate directory before, but by far my favorite method is to just let ~ be a git repo. It's maximally simple, no other tooling needed besides git.

There are a few key steps to making this work well:

• echo '*' > ~/.gitignore: This way git status isn't full of untracked files. I can still git add -f what I actually want to track.
• git branch -m dots: For clarity in my shell prompt.
• [ -d "$HOME/.local/$(hostname)/bin" ] && PATH=$PATH:$HOME/.local/$(hostname)/bin and similar if there's config I want to apply only to certain hosts.