accelbred

Are they mechanical keys?

Typing on ortholinear is quite uncomfortable for me. I find column staggered to be far better. Also why would someone learning a new layout pick Dvorak when there are better alternatives like Colemak, Workman, or Colemak mod-DH? Theres softer mechanical keys too like silenced linears.

North facing is needed for backlit keycaps, and south facing is needed for cherry profile (not the common OEM profile) keycaps. If using OEM/XDA/DSA there wont be interference with north facing. South facing does prevent use of through switch leds with at least OEM profile. Personally, I use south facing since I use SMD rgb and transparent housings with POM keycaps and the leds on the front look nice.

I'd swapped to 60% so I could put my mouse where the rest of the keyboard used to be. With home row front and center on a full size the mouse was way to the right which is quite uncomfortable. Moving to 60% was a major improvement.

Dark mode is useful because its always usable regardless of screen brightness. Who wants to be chaining their brightness all day? Also for high contrast, white text on black is always readable while the reverse is not true, limiting the contrast.

And the points you mention are not a problem with dark mode but with low contrast. These can be fixed by increasing contrast.

Ubuntu's kernel isn't exactly keeping up to date though. I assume the person you were replying to may be following mainline.

As someone using new kernel version as they are released, I'm not willing to use a filesystem that may break with a kernel update. It also seems openzfs only supports up to kernel 5.6, according the the github release. I'm on 5.9, so its not even an option.

I use btrfs, and the main reason I don't consider zfs instead is that zfs doesn't use the regular linux fs page cache. That and the fact that I use latest mainline kernel, so dont want to have to deal with kernel updates breaking zfs or tanking its performance, as when it lost access to the simd functions. The main feature I would want from zfs would be tiering, which can be gotten from btrfs on bcache, which is what I will likely use in the future. I think there was some issue with adding disks in zfs too? Don't exactly remember about that.

If git repositories didn't need a -f to rm I wouldn't, but its a habit from git repos giving errors.

Yes, and btrfs's raid1 isn't a mirror. Btrfs's raid1c3 and raid1c4 are its alternative to raid5/6 without the write hole.

BTRFS raid1 isn't mirroring drives though, it means there are two copies of each extent across the whole set of 2+ drives. and BTRFS and raid1c3 and raid1c4 are 3 and 4 copies.

If you're using RAID-Z on zfs, your comparison isn't fair. Rather than use RAID56 with btrfs, the equivalent would be to get 1 or 2 disk redundancy with raid1 or raid1c3.

Current Gentoo user. I find the opposite. Using unstable, things just work. Sometimes package updates fail to compile but your system is still fine, and the package will get fixed eventually. Never had an update break my system on unstable. Stable often had issues, which I presume is due to devs mostly working on unstable.

Ad blockers' functionality has been limited on chromium due to changes in the extension API, though

I was reminded of php's variable variables [1], which often makes for a good joke.

[1]: https://www.php.net/manual/en/language.variables.variable.ph...

That's why I use "Dark Background and Light Text". Color schemes are not as good as Dark Reader, but it doesn't noticeably affect performance.

Firefox didn't remove it. They just put it behind a new flag that is default off. Apparently it was because it affects performance for those not using the feature.

One thing to note, is that using a PID namespace in that way is incorrect. PID1 in a PID namespace has to perform the duties normally performed by a PID1, so you will normally want PID1 in the namespace to be a minimal init. If not, there may be issues, like unreaped zombie processes.