Badabinski

Many people do. I’ve remapped caps lock as escape because I am a shitty vim user who trys to solve all problems by smashing that motherfucker into itself. I noticed my left pinky was getting unhappy with me, so I tried using caps lock for esc instead and haven’t gone back.

A key dedicated to SCREAMING just isn’t that useful IMO.

I don’t have vision problems and I hate the low contrast text being shoved into everything. I’ve no idea how frustrating it must be if you have sight issues, but I can imagine.

I’ve been very pleased with my factory-seconds Framework 13 (11th gen i7, 64 gigs of RAM and 2TB storage acquired through other channels). Linux support has been basically perfect for me, although there were some kinks earlier on. The Framework 16 might work for you if you need something with a discrete GPU.

If you want something more mainstream, ThinkPads are often great for running Linux. Not every model is perfect, so I’d recommend doing some research there. The Arch Linux wiki often has laptop specific web pages that show how well supported the laptop is. For example, here’s the page for the Framework 13.

Onshape is an okay option for Linux (I’ve been able to do everything I used to to in Inventory), although I hate that it’s cloud based. I know that a rug pull is inevitable, but I figure I’ll stick with it until then.

rsync -avr --progress in termux or a file explorer app built on top of scp or rsync. It doesn’t work like your use-case, but I’ve been happy with it.

Sounds like you may want to use a union filesystem like overlayfs. I’m not sure if the specific behavior of overlayfs will work for you, but it’s worth investigating.

Thank you for putting your use-case in your post, since otherwise I think this might be an XY problem.

EDIT: There’s also mergefs and unionfs. I don’t know what the features and drawbacks are for these three union filesystems. mergefs seems like it might be the most configurable, but it’s also FUSE. unionfs and overlayfs are both in-kernel, so they’ll perform better (which may not matter for your use-case). overlayfs is the one I’m most familiar with of those two, since it’s used by most container runtimes.

Oof, I didn’t know that about firejail. I’d heard of it, but I’d never used it. Like, c’mon folks! If you need privilege escalation, either require launching as root (if appropriate), or delegate the responsibility to a small, well-audited tool designed explicitly for the purpose and spawn a new privileged pid. Don’t use SUID. You will fuck it up. If you reach the point where setuid is your only option, then you’ve hopefully learned enough to rearchitect to not need it, or to give up, or use it if you’re, say, someone who maintains a libc or something.

EDIT: this is overly dramatic, but also it’s not. I personally feel like using SUID is kinda like rolling your own crypto in terms of required competence.

Does runit have the equivalent of systemctl --user for managing per-user daemons like pipewire? I had some issues with pipewire recently and being able to journalctl --user -u pipewire and systemctl --user restart pipewire was a total godsend for me.

Yeah, every now and then I take a step back and say “what the fuck did they build?” when dealing with some of the GNU tools. Twenty minutes later I’ll start complaining about how the BSD version of something from coreutils lacks a GNU argument that would make my life about 83% easier.

It’s like a sick sort of Stockholm Syndrome. I do genuinely like GNU coreutils, but there’s some baffling shit present.

For those who don’t know (including me):

Shotcut is a free, open source, cross-platform video editor.

I could see the NT kernel being okay in isolation, but the rest of Windows coming along for the ride puts the kibosh on that idea.

I liked how each of the sections ended with a different game that she’s gotten running so far. It makes the article feel like a progressively bigger flex, which, of course, it is. Awesome to see this work progressing!

The arch wiki has a udev rule that can automatically do something if the battery crosses a certain threshold: https://wiki.archlinux.org/title/Laptop#Hibernate_on_low_battery_level

No polling which is great. I always try to do stuff on an event driven basis where possible for efficiency reasons. Gotta test this out though, since your battery might not send events for every percent change.

oh fuck I did misread it. Man, now I sound like a big ol’ asshole. Sorry, OP :/ I had a bad week thanks to some ChatGPT code and just kinda jumped out when I saw the word “ChatGPT” next to Bash.

Ugh, I hate ChatGPT. If this is Bash (which it is, because it’s literally looking for files in a directory called ~/.bashrc.d), then it should god damned well be using syntax and language features that we’ve had for at least twenty fucking years. Specifically, if you’re writing for Bash (and not POSIX shell), you better be using [[ ]] rather than [ ]. This wiki is my holy book I use to keep the demons away when writing Bash, and it does a simply fantastic job of explaining why you should use God damned double square brackets.

ChatGPT writes shitty, horrible, buggy ass Bash. This is relatively decent for ChatGPT (it even makes sure the files are real files and not symlinks), but I’ve had to fix enough terrible fucking shitty AI Bash to have no tolerance for even the smallest misstep from it.

Sincerely, A senior developer who is known as the Bash wizard at work.

EDIT: Sorry, OP. ChatGPT did not, in fact, write this code, and I am going to leave my comment here as a testament to what a big smelly dick I was here.

For me, it’s Arch for desktop usage. When I first started using Arch it would not have been Arch, but now it’s Arch. The package manager has great ergonomics (not great discoverability, but great ergonomics), it’s always up to date, I can get a system from USB to sway in ~20 minutes (probably be faster if I used the installer), it’s fast because it doesn’t enable many things by default, and it’s honestly been the most reliable distro I’ve ever used. I used to use OpenSUSE ~10 years ago, and that broke more in one year than Arch has in ten.

I personally feel like Arch’s unreliable nature has been overstated. Arch will give you the rope to hang yourself if you ask for it, but if you just read the emails (or use a helper that displays breaking changes when updating like paru) and merge your pacnews then you’ll likely have a rock solid system.

Again, this is all just my opinion. It’s easy for me to overlook or forget all of the pain and suffering I likely went through when learning how to Arch. I won’t recommend it to you, but I’ll happily say how much I’ve come to enjoy using it.

What if you need to file a bug? What if you have a question on the config that’s not easily answered by the docs? If you never, ever find bugs and never, ever have questions, then sure, separate the two. There are genuinely people like that, but they’re not common. If you’re one of them, then I’m genuinely glad for you.

My opinion is this: You use software. You don’t use people, but you sure as hell rely on them.

Because Vaxry (the lead dev) got banned from contributing to wlroots or any other FDO projects.

As for why he was banned, this is the only thing I’ve read about the whole thing: https://drewdevault.com/2024/04/09/2024-04-09-FDO-conduct-enforcement.html

Basically, he violated the FDO Code of Conduct when being told that a particular thing he said/enabled in a Discord community would not be acceptable if it was seen in spaces covered by said CoC.

This appears to be his response.