31–40 of 108 posts
Why don't people just use make?
The author's npm scripts approach is great for a small scale project needing to run just jshint but if you start getting into something serious, running more than one task multiple times is a serious dent in your workflow.
And grunt/gulp for complex projects. grunt, cause it is simpler than gulp, but only when it match the projects use case.
gulp for "live" things, like livereload or quick partial builds on developement.
Startet now to use webpack too, it is comfortable (campared with grunt), it does many build-stuff that you define in grunt by your own.
Like always, use the right tools to get the job done.
It exist not THE one and only tool that solve all problems in the world.
I simply use Make for all my web projects, whether it's a Ruby JSON API, or a React front-end. It's reliable, pre-installed everywhere, and can wrap anything in one consistent CLI. Why have to remember whether to type lein repl , pry , or rails console , when make repl will do everytime? Ditto, bundle install , npm install , lein deps => make deps . make server can easily wrap whatever command launches the server, ma…
I simply use Make for all my web projects, whether it's a Ruby JSON API, or a React front-end. It's reliable, pre-installed everywhere, and can wrap anything in one consistent CLI. Why have to remember whether to type lein repl , pry , or rails console , when make repl will do everytime? Ditto, bundle install , npm install , lein deps => make deps . make server can easily wrap whatever command launches the server, ma…
Also some plugins are complicated (or dynamically) to configure. His examples were very simple, he could just put it into a batchfile aswell.
This article seems super weird -- do people actually use Grunt/Gulp to run a single command at a time? Most uses that I've encountered are along the lines of 'we've got this huge build process involving compass, sass, uglify, ng-annotate, and 13 other things', and Grunt/Gulp allow you to do the whole thing, automatically re-running on file changes, with a single command.
tl;dr: The author meant to say "Use Browserify instead of Grunt/Gulp" but then got all confused and wrote some unrelated stuff about how npm has a case..esac statement built in. While we're at the subject, might I suggest using webpack instead of browserify? It's roughly the same, but less buggy.
Why don't people just use make?
People are scared of significant whitespace or old software or something.
For years, the front page of Ant had a rant towards Makefiles on it, including this highly unprofessional quote: '"Is my command not executing because I have a space in front of my tab!!!" said the original author of Ant way too many times.'
https://web.archive.org/web/20100203102803/http://ant.apache...
They only removed it in 2010 with the release of 1.8.0.