In the world of build scripts, both Gulp and Grunt have become quite popular, and each has its own share of proponents, critics, loyalists as well as fans.
The battle continues. And (not) surprisingly, it linked to previous post too.
Just when starting to use Grunt, now should stop? 😄
Stephan Max shows how to build your own little Grunt plugin and publish it via the npm package manager.
This is a good tutorial. But since won’t create one in the near future, just skim it for now.
Microsoft’s Etienne Margraff explains how to use developer automation software like Gulp and Grunt to make your development workflow simple.
Gulp sounds promising. But like ever read somewhere (forgot the link), if Grunt is enough for doing the jobs, then won’t necessary to learn the same tool.
And here’s another quote to strengthen the statement:
If you are using a really standard workflow with common steps like jshint, uglifying, css validating etc., Grunt is a good choice. If you are up to more complicated tasks, gulp will be a good wingman.
Louis Lazaris has discovered a slew of new tools for front-end developers. In this end-of-year post, he lists some of his favorite finds of 2015.
Let’s wrap things up. Part 1. Total 6 articles.
I asked front-end developers to fill in a survey about their their knowledge and usage patterns across a number of front-end tools. Check out the results.
Surprisingly, Gulp is used more than Grunt. Time to change, too? Or just stick with Grunt? And this “module bundler” seems like things to catch. Never used/heard before.
Good introduction. And it has both Grunt and Gulp in one post. Even though it’s sponsored, but definitely good read. Favorited.
Chris Coyier grabs Grunt by the snow-white fur of its Santa suit and places it firmly (but gently) in your webdev grotto to dish out its Christmas gifts — and maybe even chuck you under the chin and sit you on its broad and comfy knee. Not at all creepy. No. Nope.
From the article:
Feels pretty comfortable at this point, hey? The only weird bit there is the
spawnthing. And you know what? I don’t even really know what that does. From what I understand from the documentation it is the smart default. That’s real-world development. Just leave it alone if it’s working and if it’s not, learn more.
Nouran Mahmoud introduces Jade, a Node-based template engine to preprocess your HTML, demonstrating how to automate HTML production with Jade using Grunt.
Already use Jade for production. But this give a good base understanding. Also mixins and stuffs give a deeper knowledge. Going to try that in another time.