25
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Jul 2024
25 points (100.0% liked)
TechTakes
1385 readers
114 users here now
Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.
This is not debate club. Unless it’s amusing debate.
For actually-good tech, you want our NotAwfulTech community
founded 1 year ago
MODERATORS
this is awesome
but this is making me go “fuck yeah” on the inside. it seems like a small change, but I can’t emphasize enough how frequently this command gets used (for every flake dependency, not just nixpkgs) for how longwinded and non-memorable the old form of it was. it’s kind of fucking incredible how many UX warts Nix has just from the old evaluator’s devs digging in their heels on shit like this.
which reminds me, I need to check if lix/aux are going to do a cli-side nixpkgs search with a reasonable invocation
what do you mean you don’t like when your package search command is one of several random, probably-unmaintained ecosystem packages that has to very slowly index everything every time nixpkgs updates because it doesn’t have access to the evaluator’s internals?
I keep getting the itch to do something like that old hfimd page for a variety of ops infrastructure tools, because fucking hell