It's unreal. I've packaged so many super daunting packages that would take myself weeks to package (and some that I've tried and failed to package). I have 6 years of daily driving nixos...So I'm not exactly new to the distro.

Even messing with stdenv or language builders is trivialized. Any software that I want, I can get within a few hours of claude/codex just spinning unsupervised. It's so nice! Underrated for sure.

And if you watch what it's actually doing during a session like that, it's basically exactly what a human would do: run the build, find the error, google the error, consider 2-3 possible fixes, pick one and apply it, repeat. Afterward, look at the various patches and fixups and decide if a refactor is necessary.

can I use this in neovim? Something like fzf.vim

I have created a vim plugin that works both in vim and neovim which you can find at https://github.com/prabirshrestha/tv.vim

Just added it to the showcase section https://github.com/alexpasmantier/television/wiki/Showcase if you wish to add any details :-)

It's a show stopper that there's no macos support (afaiu). Eagerly awaiting that...

I believe you're referring to:

> Store-based systems, however, are static in nature, with all dependencies being resolved at build time.

I think the author is saying that the shared libraries (.so) are available at build time on store-based systems and never change. Thus, the dynamic linker can speed up symbol resolution by doing the symbol resolution at build time and sticking the result in output binary. This is distinct from static linking which sticks the entire library (.a) into the output binary.

You clarified correctly (author)

Thank you both, clearly it was I who was confused!

I would love to use this, but I can't figure out how to install it on my M1 mbp.

The website (at Download Nyxt 3.0.0) mentions:

> macOS is not officially supported by Nyxt. An official port is currently in development. Unofficial, and older ports are available below: Docker, Macports.

While Docker would work on a Mac with ARM, Docker on macOS is still slow AFAIK and a full-blown Linux VM. It also requires X11, the documentation mentions XQuartz. Hence, I'll skip this software, for now.

Indeed, we're working on it now. We even have a branch now :-)! Please stay tuned!

This is incredibly exciting. Let me know if I can help test! Where does the branch live?

Nix has a debugger now. You can drop into the frames that are causing problems and inspect the state. Miles easier than looking at the trace manually.

I last flashed my flake.lock in June, so I might be out of date, but my rigs can’t reliably include the line number in my code that led to the duck-typing fiasco deep in the core of someLanguage.withPackages.fuck.WTF.this.

Fix the fucking “—show-trace” thing folks. Seriously.

Out of all cases when I used --show-trace, I can remember it being useful only once or twice. I gave up and just sprinkled builtins.trace.

IIRC debugger comes with nix 2.9 and nixpkgs for 22.05 still has 2.8.x.

I was excited to see the debugger flag to nix build the other day, since I'm really struggling cross-compiling an RPi on BTRFS root sd image.

Of course running with the debugger flag resulted in an unintelligible error message and no debugger.

Any link to documentation on how to use it? Would be a godsend for me