Your documentation on file system choice is either anecdotal or engineering-masters-thesis, seemingly no in-between

God, I feel this so much. All the benchmarks are such ass too.

I have also struggled with picking a disk layout + FS, and landed on using a single BTRFS partition with FDE.

For now, I’m happy. Unless there’s a new FS that definitively beats BTRFS on NVMe perf and supports copy-on-write and something that makes FDE as easy as subvolumes that definitively beats BTRFS on NVMe drives, I won’t even bother looking into it again.

I’ve considered moving to a RAID setup, but it seems like more trouble than it’s worth, since I do regular /home backups & NixOS keeps my entire system config in version control.

If I ever consider a different disk setup, I’m just going to fire up a clean distro install on a spare NVMe and benchmark my most common tasks myself.

NixOS has killed my decision paralysis for choosing distros and desktop env stuff since I can just enable whatever in my config, try it out, then revert if I don’t like it enough to switch.

Only thing I can’t trivially test is disk layouts, but with disko, it might be easy enough to create a custom NixOS installer that:

• auto-installs a disk layout & your config
• reboots
• runs your benchmarks
• writes the results to disk
• reboots into the live image, repeating this for a list of disk layouts.

Boomers are just itching to drop this line on the closest service worker they can find.

I assume its because theyre thinking the service worker will also be mad about people receiving government benefits because they’re employed.

Turns out service workers aren’t as fond of regurgitating the agitprop of capitalists as wealthier boomers who grew up in a more affordable era.

If you didn’t want them to have solidarity with the unemployed, you shouldn’t have made life so expensive and employment so precarious.

USA 2024 values

I reallt like the approach taken in Rust’s borrow checker, where good, safe, and sometimes overbearing design choices are enforced by default, but you can explicitly declare exemptions. Makes identifying potential problem code blocks easy too.

Gotcha! I’ll have to look into it. I heard of it being used with Rust, which is probably the only lang I want to use for backend anymore. If it minimizes JS boilerplate, that’s a big win.

Part of the problem is choosing from those options (when you have a choice). Open-ended questions like that nuke my productivity when starting a project because I spend more time researching and weighing options than actually programming.

As time has gone on, I’ve increasingly become a fan of restricting how many ways devs can do something.

you just pick one and go with it.

Might be my ADHD, but I can never just do that. But I posit that excess choice hurts feature development pace by wasting effort on reinventing the wheel.

A good example is the Nix ecosystem:

Nix expression language provides almost no constraints, leaving users to do the same things in a bunch of ways, and preventing a clear notion of which way is generally best from arising…which makes upstream super conservative with implementing new features the community wants, because any decision might break one those things. Leaving us with a 5+ year old “experimental” feature + CLI used by 80% of users, but no consensus on an official implementation. So many simple upstream changes become a series of 3 competing community projects providing a solution for that feature, further preventing consensus.

The 15+ electron apps on my devices would like a word with you. I think I dislike JS more as a user than a dev because at least Typescript exists now.

Wait are people writing Go for frontend code now? Or do you mean just replacing the node back end with Go?

I’ve heard nothing but good things about HTMX. I might have to play around just to get a feel.

Every person I know who used JQuery seems to really miss it. My only impression of it is that it looks goofy. Similar for PHP, but my only experience with it is Nextcloud causing me nightmares.

Also missing SASS/SCSS/Tailwind, bootstrap, and Babel

All of these bring me a sense of dread, each in a unique way.

Java I have a special loathing for, but the ecosystem isn’t too wild, just verbose and so XML heavy.

JS is its own hell because of the sheer number of permutations of technologies a given project will use. There’s always at least one nonstandard framework or tool lingering around from an old trend.

Python reimplemented the same dep management wheels 5x each, and I have no idea what common stacks look like anymore, but every time I encounter Python projects, something is always broken.

C is nice and easy from what I’ve used (just GCC & make), but idk what complexity arises in bigger projects.

Just so glad I’m not a webdev anymore and work with mostly just Rust, cargo, and containers.

I think the ActivityPub sphere needs to transition from “fedi replica of X service” to “Y component that would be useful to existing fedi services”.

Event planning is one of them. Simple, encrypted one-to-one DMs is another. Moderation tools is a big one too.

Would be a shame if each software has to independently reimplement the same features desired by each flavor of threaded reply service.

I like this as an idea, but there’d need to be some sort of automatic hooking for me to want to use it. eza/lsd are good enough for ls output for me.

Doing stuff like this is much more cozy in nushell, since piping is a lot less messy

I find myself writing way less stuff like this since making the switch…partially because they output of a lot of builtins is already pretty.

Dolstra definitely did some shit wrong tho.

stoopid tankie, getting high on sources

is there a tool that also works with other git forges like GitLab and Forgejo?

rare blur setup that both looks good and practical without being super tacky. What is the blur algo?

maybe they should consider doing that instead

Sounds good in theory.

But I’ve had so many issues with D-Bus fucking shit up on my systems that I’d be very reluctant to hinge my only way of recovering from failures upon something so brittle.

Granted, D-Bus hasn’t given me any trouble since moving to NixOS. The hell of trying to recover my arch systems from a perpetually failing D-Bus would make me very apprehensive to adopt this. I could see myself using run0 by default, but keeping sudo-rs or doas around with a much stricter configuration as a failsafe until the run0 + D-Bus + PolKit is absolutely stable and bulletproof.