So how would I do a watch task, recompile less and minify js when files changes?
These tools are there for a good reason.
Why we should stop using Grunt and Gulp
41–50 of 108 posts
Re: Why we should stop using Grunt and Gulp
#42Why don't people just use make?
It's hell for those of us outside of the Unix ecosystem. I have MSYS on my Windows machine and make works only half of the time.
Also the learning curve is just not as easy, nor the files as readable. With Gulp and Grunt you are exploiting the fact that almost everyone can write a couple of lines of JavaScript. The only thing you are adding is an api composed of three to four functions.
If you look at make on the other hand, you'll need to learn quite a lot.
Re: Why we should stop using Grunt and Gulp
#43My vote is for bash scripts. If you are in Windows then you can use babun or preferably get off Windows.
Re: Why we should stop using Grunt and Gulp
#44If you want something like grunt but simple you can try the thing I made which is called 'bild'.
Re: Why we should stop using Grunt and Gulp
#45Why don't people just use make?
It's hell for those of us outside of the Unix ecosystem. I have MSYS on my Windows machine and make works only half of the time. Also the learning curve is just not as easy, nor the files as readable. With Gulp and Grunt you are exploiting the fact that almost everyone can write a couple of lines of JavaScript. The only thing you are adding is an api composed of three to four functions. If you look at make on the oth…
Yes I'm on windows and already had the case of a npm package I would have liked to contribute but the build process was using make, couldn't make it work...
It's a bit disapointing when you have a very good multiplatform ecosystem to see stuff like that, sometimes it's people "forgetting" there's also windows (and I can get that), but some other times it's just a big "fuck you windows user".
Re: Why we should stop using Grunt and Gulp
#46tl;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.
How is Browserify/Webpack a replacement for Grunt/Gulp? Genuine question.
They have their own plugin/watching systems, I'm trying webpack on a project and I'm just starting it with a "npm run" command.
Re: Why we should stop using Grunt and Gulp
#47I found all build systems for all platforms to be a total PITA and eventually i just resort to using a shell or python script to invoke the commands i want. With this method you can very easily add user promting (do you want to build debug or release?), database reporting of build and test results, source control integration etc. Whatever i learn here can be applied and reused for new things in the future instead of…
You still have to get all tools to all build environments (developer computers, build servers). For javascript you can write the build script in javascript without Gulp, Broccoli or Grunt, it works great. But you still want some tools to be installed and then you probably start to use NPM anyway.
Re: Why we should stop using Grunt and Gulp
#48What NPM can't do is the async workflow of Grunt watch (or serve) and dynamically trigger specific (sub)processes in real-time. Turns out, this is the main way I'm using Grunt. Also some plugins are complicated (or dynamically) to configure. His examples were very simple, he could just put it into a batchfile aswell.
I think Broccoli looks great for simple watch things.
Re: Why we should stop using Grunt and Gulp
#49I found all build systems for all platforms to be a total PITA and eventually i just resort to using a shell or python script to invoke the commands i want. With this method you can very easily add user promting (do you want to build debug or release?), database reporting of build and test results, source control integration etc. Whatever i learn here can be applied and reused for new things in the future instead of…
You cannot compare something like Maven/Gradle/SBT/Leiningen to Make.
Make doesn't do incremental building and testing, it doesn't do test coverage reports, it doesn't download the dependencies for you, it doesn't build the Javadoc documentation for you, it does not package and publish your signed artifacts on Maven Central, it does not wrap your stuff in an OS specific installer, etc, etc...
And you know, these things are standard stuff that one would like to do for every project. It's unfathomable why anybody would want to do this manual plumbing for each project with Make. You call Make "simple", I call it "dumb" and it's the reason for why people end up with aberrations of nature, such as Autotools.
> Gradle requires you to read the first 12 chapters of the manual before you can even begin doing something more advanced than running compile
You're exaggerating. Compiling a project is a hello world of a couple of lines. What "advanced" usage are you talking about anyway?
Re: Why we should stop using Grunt and Gulp
#50tl;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.
What are the most serious bugs in browserify?