3 ms·

Agreed if you only have to support linux/unix, but the one good thing about the Node ecosystem is that they tend to work on windows too.

gjvc 5y ago
not the point, also "WSL"
verelo 5y ago
While i agree, I’ve spent literal days fighting with node modules in recent months. Sure make isn’t perfect either but it’s a lot less, confusing? Ie json isn’t a language for humans, but often you really need to read it to correct some issue or bad merge from another contributor.
- nicoburns 5y ago
  > Sure make isn’t perfect either but it’s a lot less, confusing? I think that's a matter of what you're used to. I don't use make all that often, so I find make files beyond a few lines quite a lot to get my head around, whereas I spend all day writing JavaScript so I can read/write JSON in my sleep.
  - verelo 5y ago
    Maybe. I actually use node much more often, i don't even recall the last time i used a make file in production, i just find parsing json as a human to be rather painful.
Steltek 5y ago
Make has worked on Windows longer than Node.js has existed.
- nicoburns 5y ago
  Make works fine, it's the commands you call from make that don't tend to as compatible. For example, try running rm -rf on windows. It might work if you have GNU tools installed, but it certainly won't work out of the box. On the other hand, the node.js `rimraf` package will do the same thing with no cross-platform compatibility issues.
  - Steltek 5y ago
    When using package.json, does npm intercept a script containing "rm -rf" and translate it to something different?
    - geewee 5y ago
      No, that's why there's a bunch of packages such as rimraf[0] that implements that sort of functionality in a cross-platform way that most people use in their scripts [0]: https://www.npmjs.com/package/rimraf https://www.npmjs.com/package/rimraf
    - nicoburns 5y ago
      No, but it does put binaries from any installed node packages in your PATH (locally when running scripts).
- jchw 5y ago
  The history of Make on Windows would Make one think twice about relying on it. What shell do you get when running Make on Windows?
throw0101a 5y ago
http://gnuwin32.sourceforge.net/packages/make.htm http://gnuwin32.sourceforge.net/packages/make.htm https://community.chocolatey.org/packages/make https://community.chocolatey.org/packages/make

gjvc 5y ago

not the point, also "WSL"

verelo 5y ago

While i agree, I’ve spent literal days fighting with node modules in recent months. Sure make isn’t perfect either but it’s a lot less, confusing? Ie json isn’t a language for humans, but often you really need to read it to correct some issue or bad merge from another contributor.

nicoburns 5y ago
> Sure make isn’t perfect either but it’s a lot less, confusing? I think that's a matter of what you're used to. I don't use make all that often, so I find make files beyond a few lines quite a lot to get my head around, whereas I spend all day writing JavaScript so I can read/write JSON in my sleep.
- verelo 5y ago
  Maybe. I actually use node much more often, i don't even recall the last time i used a make file in production, i just find parsing json as a human to be rather painful.

Steltek 5y ago

Make has worked on Windows longer than Node.js has existed.

nicoburns 5y ago
Make works fine, it's the commands you call from make that don't tend to as compatible. For example, try running rm -rf on windows. It might work if you have GNU tools installed, but it certainly won't work out of the box. On the other hand, the node.js `rimraf` package will do the same thing with no cross-platform compatibility issues.
- Steltek 5y ago
  When using package.json, does npm intercept a script containing "rm -rf" and translate it to something different?
  - geewee 5y ago
    No, that's why there's a bunch of packages such as rimraf[0] that implements that sort of functionality in a cross-platform way that most people use in their scripts [0]: https://www.npmjs.com/package/rimraf https://www.npmjs.com/package/rimraf
  - nicoburns 5y ago
    No, but it does put binaries from any installed node packages in your PATH (locally when running scripts).
jchw 5y ago
The history of Make on Windows would Make one think twice about relying on it. What shell do you get when running Make on Windows?

throw0101a 5y ago

http://gnuwin32.sourceforge.net/packages/make.htm http://gnuwin32.sourceforge.net/packages/make.htm https://community.chocolatey.org/packages/make https://community.chocolatey.org/packages/make