2 ms·

How's the package parity? Have you run into any packages you can't find for nix for OS X?

• thinkpad20 10y ago
  There are a number of these, but most of the big ones are supported (e.g. emacs, vim, python and most common pypi packages, ghc and most haskell packages, ssh, git, ssl, blah blah blah). The main challenge with supporting OSX is that the closed-source nature and/or proprietary license of a lot of the low-level system libraries, especially for graphical applications, doesn't play very well with nix, which does best with HTTP URLs from which (preferably) source code and/or (failing that) prebuilt binaries can be fetched, the contents of which are deterministic. That said, there are tens of thousands of packages that build on OSX, certainly many more than enough to be a very useful platform for package management, especially when coupled with all of the advantages that nix brings. The downsides are a higher learning curve and occasional missing and/or broken packages.
• hkjgkjy 10y ago
  There has been a few times I couldn't find more obscure packages on there. I still keep brew installed on my machine, where those packages are available. Wish there were more friendly (ruby-esque and fun like homebrew) tutorials on how to create packages. I hope to use Nix for go and c programs the same way you use Boot/Lein, Maven, Bundle and Npm for their respective tasks - make a manifest local to a project directory. No more figuring out whatever that library is called in my package manager...