| ▲ | skavi 2 days ago |
| where does this fit in with make, just, nix (devshell, devenv, ...), direnv, etc. |
|
| ▲ | mgrandl 2 days ago | parent [-] |
| It basically does replace make/just, nix, direnv in one convenient binary. It’s very pleasant to use. |
| |
| ▲ | steve_adams_86 2 days ago | parent | next [-] | | How is it more pleasant than the others? I've used make and nix, but not extensively. They seemed fine. Make seemed extremely powerful if a little rough on the edges at times. Nix was not super intuitive and I was never content with it before leaving it behind. That was probably a me-problem, because I could tell it was very capable and designed well in some ways. | | |
| ▲ | ElCapitanMarkla 2 days ago | parent [-] | | I came from dealing with various node / ruby / python versions across multiple projects where I used nvim / rbenv and some python manager. Miss is nice as you can just switch to it and not relearn anything, it just works with the old configs. I haven’t tried make with our setup but nix was too much of a hassle. Especially when some projects required old versions of libraries across dev (macOS) and staging/prod for various Linux OS. |
| |
| ▲ | skavi a day ago | parent | prev [-] | | i assume it does not have the same goals wrt hermeticity as nix? | | |
| ▲ | piperswe a day ago | parent [-] | | Correct, for the most part it uses the binaries distributed by the upstream project. |
|
|