A few from Itch, Parallel Launcher from Flatpak for SM64 hacks
You're deluded if you think that "everybody" let alone a large minority of people say that the Linux desktop is "good, perfect and polished".
Our group did a two-part Microscope-like after a "season" of 14 sessions to wrap up a ton of loose ends and set up the next season. It was super satisfying to zoom in on only what the players wanted to see and resolve.
Our first session of January is going to be another Microscope session too, we've got a giant pointcrawl to backtrack and see the fallout of our action or inaction.
I get your point. Since a .tar.zst file can be handled natively by tar, using .tzst instead does make sense.
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.
*Thank you engineers who happen to be working at Facebook
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.
Typically find "$HOME/docs", but with a few caveats:
-
In Zsh or Fish, the quotes are unnecessary:
find $HOME/docs -
If I'm using anything potentially destructive:
mv "${HOME:?}/bin" ... -
Of course, if it's followed by a valid identifier character, I'll add braces:
"${basename}_$num.txt"
My Linux review: 10/10, would recommend, but would not install for someone and let them use it for the next 5 years.
"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 waygit statusisn't full of untracked files. I can stillgit add -fwhat 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)/binand similar if there's config I want to apply only to certain hosts.
Yeah, most distros will set up
sourcechains to make things nicer for users.