4 ms·
Not disagreeing, but isn't npm / yarn being installed basically the same as having make / cmake installed? This package in question has no dependencies and I c
by dncornholio 3y ago
Not disagreeing, but isn't npm / yarn being installed basically the same as having make / cmake installed?
This package in question has no dependencies and I can read the source code, can't do that with a binary.
Though I agree, but for other reasons, this tool is a bit silly in JS because you also need node, and it's basically just moving files around.
- Zandikar 3y agoNo. Not everyone lives in Javascript world.
- westernpopular 3y agoNot everyone lives in C world either
- sitzkrieg 3y agobut some OS do by default-ish :D
- deleted 3y ago[deleted]
- Zandikar 3y agoCorrect. These are not mutually exclusive positions, and furthermore, this isn't so much to do with languages necessarily, it can be written in brainfuck or use some obscure compiler for all I care. The issue is fragmenting tools between multiple package managers. That's a pain, and the source of my opposition to this concept here. Doubly so if they're language specific package managers (fine for development/in isolation, not for system wide user facing tools though).
- seszett 3y ago> isn't npm / yarn being installed basically the same as having make / cmake installed? Not really as npm and yarn are whole package managers that work in parallel to your distro's standard package manager. They pull various sources (that haven't been vetted by anyone except hopefully by the end programmer who told you to use npm install) from who knows where and install them either in your own home, or system-wide with -g like suggested here. I would never use npm to install a system tool.
- tracker1 3y agoSo like anything else that isn't in your package manager... including the latest version.
- tcfhgj 3y agoI dont have (c)make installed