I like make but I don’t understand the logic here. If you’re going to install node anyway, why be so against using node for scripts? Perhaps less of an issue these days but make also isnt included in windows.
The article makes this pretty clear. Some of us work simultaneously in different stacks: js, python, php, go, whatever... each and every one having their own dependency/building tools. Having a consistent DX (make this, make that) across all projects has value.
One reason the article points out is to make the developer experience "portable" between projects regardless of underlying technology platform/framework.
That is not necessarily something everone agrees with ("when in Rome" etc) but it is a reason.
Comments
I like make but I don’t understand the logic here. If you’re going to install node anyway, why be so against using node for scripts? Perhaps less of an issue these days but make also isnt included in windows.
The article makes this pretty clear. Some of us work simultaneously in different stacks: js, python, php, go, whatever... each and every one having their own dependency/building tools. Having a consistent DX (make this, make that) across all projects has value.
One reason the article points out is to make the developer experience "portable" between projects regardless of underlying technology platform/framework.
That is not necessarily something everone agrees with ("when in Rome" etc) but it is a reason.