3 ms·
Been using nix for a few weeks and while I feel like it really has some great ideas, here are what my pain points have been: - not great documentation, especia
by baby 4y ago
Been using nix for a few weeks and while I feel like it really has some great ideas, here are what my pain points have been:
- not great documentation, especially for newer features like flakes
- nix wants to replace rustup when rustup is already doing great
- nix doesn’t seem to work that well on mac. Not sure if it’s our config our that it’s painful on mac in general
- the biggest issue: it doesn’t work well with tools (vscode, sublime merge, etc.) as you need to launch them within a nix shell and that doesnt work well (at least on mac). Now I’m wondering if it’d make sense to install tools within the flake dev shell…
- rgoulter 4y ago> the biggest issue: it doesn’t work well with tools (vscode, sublime merge, etc.) as you need to launch them within a nix shell and that doesnt work well (at least on mac). In what sense? In terms of "some nix shell provides some tools, and VSCode can't see those".. direnv is one way to work with this. e.g. direnv integrates with nix to integrate the nix shell at that path, and a direnv plugin for VSCode etc. can pick up the direnv file, so that it loads the nix shell appropriately.
- ParetoOptimal 4y agoVscode doesn't let you specify plugin load order and nix-env-selector needs to load before anything else or you can have problems last I checked.
- baby 4y agoAh that might be why I had these problems. Do you know what a solution could be?
- baby 4y agoI tried everything from direnv (with the nix direnv thing and a diverse direnv extensions for vscode) to opening vscode from a flake dev shell, nothing works on my mac