zlacker

[parent] [thread] 4 comments
1. rootno+(OP)[view] [source] 2026-02-04 15:31:05
That is quite an involved setup to get a costly autocomplete going.

Is that really where we are at? Just outsource convenience to a few big players that can afford the hardware? Just to save on typing and god forbid…thinking?

“Sorry boss, I can’t write code because cloudflare is down.”

replies(2): >>Cyph0n+6i >>groby_+cJ1
2. Cyph0n+6i[view] [source] 2026-02-04 16:47:56
>>rootno+(OP)
Keep in mind that this setup is a one-time cost. Also, a lot of the code is related to configuring it the way the author wants it (via Home Manager).

Generally speaking, once you have a working NixOS config, incremental changes become extremely trivial, safe, and easy to rollback.

replies(1): >>aquari+9J
◧◩
3. aquari+9J[view] [source] [discussion] 2026-02-04 18:42:03
>>Cyph0n+6i
To provide another data point: I too use NixOS and oh boy that one-time is really costly. And while we're sharing Nix stuff for LLMs there's this piece of kit too: https://github.com/YPares/rigup.nix
replies(1): >>Cyph0n+l91
◧◩◪
4. Cyph0n+l91[view] [source] [discussion] 2026-02-04 20:44:08
>>aquari+9J
Agreed, the learning curve is insane and docs are sparse. But it is truly worth it imo, even if you’re just using Nix as a build tool, or using Home Manager on Linux or macOS.
5. groby_+cJ1[view] [source] 2026-02-04 23:56:26
>>rootno+(OP)
If you believe "costly autocomplete" is all you get, you absolutely shouldn't bother.

You're opting for "sorry boss, it's going to take me 10 times as long, but it's going to be loving craftsmanship, not industrial production" instead. You want different tools, for a different job.

[go to top]