3 ms·
In the web world, make is effectively unheard of, or considered "too hard to use", and thus we end up with dozens of nodejs based build tools that constantly re
by stephenr 10y ago
In the web world, make is effectively unheard of, or considered "too hard to use", and thus we end up with dozens of nodejs based build tools that constantly replace each other.
I think static site gen is probably another area where make could be quite useful.
- flukus 10y agoThis predates nodejs, every ecosystem has been re-implementing make, poorly. Java has ant/maven/gradle, .net has nant/msbuild/psake. Ruby and python have their own. I wrote a post recently about using make with higher level languages (TLDR- it's much more simpler and more concise than it's "successors"): http://flukus.github.io/2016/11/30/2016_11_30_Rediscovering-Make/ http://flukus.github.io/2016/11/30/2016_11_30_Rediscovering-...
- stephenr 10y agoThat is true, but I feel like it's exposed to a broader audience in the front-end dev world: you can be a backend dev in whatever language you like and you've probably worked on a project where a front end dev has introduced some ridiculously complex build system for css files. This is literally the comment I was given by a dev who was continuing someone else's work, about how the front end assets needed to be built: i) install npm ii) install grunt globally (npm install -g grunt) iii) install bower globally (npm install -g bower) iv) install bower packages (bower install) v) install npm packages (npm install) vi) run grunt