Back up your data folks. You’re probably more likely to accidentally rm -rf yourself than download a script that will do it.

Doubt it. Why would a maintainer intentionally self sabotage their own API stability? Cutting off one’s nose to spite the face.

I got whooshed then. Maybe because I only skimmed the article to try to figure out what their point was.

Basically just tmux + Helix + fish shell.

deleted by creator

Annoyingly long post totally misses the point of using tmux and chalks it up to “elitism”. So who’s really acting like an elitist contrarian??

Do you not SSH onto your desktop? I do it all the time. I often want to switch from coding at my desk to coding on a laptop, and tmux + SSH makes that transition completely seamless.

SQLite was literally invented within the US military.

If you go this route I recommend installing Kodi + Jellyfin Plugin + Kore Android App. You can control everything from your phone or laptop.

Except the vast majority of the kernel is in driver modules.

So for an individual machine, the attack surface is not really any bigger than it needs to be.

The OS will only load modules it needs for your hardware, so the “bloat” only exists at the source code and binary size level. You are free to compile an optimized binary for your hardware. The complete kernel binary should fit in a 200MB boot partition.

As for maintenance, that’s a fair point, but the effort is at least somewhat distributed if hardware devs provide the drivers.

This would be more believable if Elon paid his cloud bills.

No doubt, but where does the documentation explain that? It’s not totally surprising that the firmware would remain closed source for now.

Regardless of the fact that firmware and userspace components are still closed source, this is still an improvement for the Nvidia + Linux relationship.

https://github.com/NVIDIA/open-gpu-kernel-modules

Nvidia released open source drivers in 2024.

I just want Sway to work on Nvidia GPU without flickering.

that’s a git problem, not Windows.

I use Git, and I don’t use Windows. I have no problems. Sounds like… a Windows problem?

You are never guaranteed to be able to do anything during a crash. You are better off handling these kinds of edge cases in a recovery phase during the start of your app.

• Has a simple backup and migration workflow. I recently had to backup and migrate a MediaWiki database. It was pretty smooth but not as simple as it could be. If your data model is spread across RDBMS and file, you need to provide a CLI tool that does the export/import.

• Easy to run as a systemd service. This is the main criteria for whether it will be easy to create a NixOS module.

• Has health endpoints for monitoring.

• Has an admin web UI that surfaces important configuration info.

• If there are external service dependencies like postgres or redis, then there needs to be a wealth of documentation on how those integrations work. Provide infrastructure as code examples! IME systemd and NixOS modules are very capable of deploying these kinds of distributed systems.

This type of shit makes me aware that there really are devs that don’t care about efficiency and will spend weeks on some really novice shit because their tools and skills are bad.

Silverbullet is nice