can I use this in neovim? Something like fzf.vim
Readit Newsgeddawm commented on Television: Fast general purpose fuzzy finder TUI github.com/alexpasmantier... · Posted by u/thunderbong
It's a show stopper that there's no macos support (afaiu). Eagerly awaiting that...
geddawm commented on Speeding up ELF relocations for store-based systems fzakaria.com/2024/05/03/s... · Posted by u/setheron
This article confuses static linking and deterministic builds. I.e Nix, a "store-based system" (author's term), still very much dynamically links. Static linking means copying actual program code from libraries into the executable itself, such that external .so files don't need to be loaded.
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.
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?
I would love to use this, but I can't figure out how to install it on my M1 mbp.
> Error messages that tell you absolutely nothing about what went wrong were pretty common.
Maybe I'm holding it wrong, but I almost never get useful error messages from Nix (NixOS and NixOps). Almost every error is deep within some module with no trace to the option I set. Just nix barfing its 300-line eval traceback where my own code doesn't even appear.
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.