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

It’s the first sentence of the article.

Anyone that thinks they’re “coding on the go” with something of this form factor is kidding themselves.

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 don’t think there is a world where Linux gains significant market share AND users care what sudo is. In order for Linux to be more mainstream, those kinds of details should not be the concern of laypeople. GUIs are what average people are able to stomach.

It’s almost 30 years old. Not to knock cURL, it’s a staple for sure.

HTTPie and xh claim to have a more intuitive UX. If the functionality is comparable, I choose tools written in memory-safe languages by default.

xh is a nice modern alternative.

There is actually a JS library called Planktos that can serve static websites over BitTorrent. I don’t know how good it is, but it sounds like a starting point.

https://github.com/xuset/planktos

deleted by creator

Organizationally, you don’t want your API handler to care about implementation details like database queries. All DB interaction should be abstracted into a separate layer.

Generally API handlers only care about injecting any “global” dependencies (like a database object), extracting the request payload, and dispatching into some lower-level method.

None of this requires generic code. It’s just about having a clear separation of concerns, and this can lead to more reusable and testable code.

Because they often won’t let you.

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.

Silverbullet is nice

Good point. There are some where it’s just a few miscellaneous files missing.

I have so many files that have been stalled at >95% for months.