News for hackers. Stuff that matters.
Re:Eliminating Code Smell with Grunt by jaredhanson on Monday December 02, 2013 @10:38AM (#6834255)
I lol'd at the title. Just having a Gruntfile is the first smell I notice when looking at a project. Seriously, why take two simple tools and layer a unnecessary "task runner" on top of them?
Re:Eliminating Code Smell with Grunt by possibilistic on Monday December 02, 2013 @11:23AM (#6834570)
What does your build process look like? What's the tooling, and how do you invoke it? Just curious about alternatives.
Re:Eliminating Code Smell with Grunt by jaredhanson on Monday December 02, 2013 @12:49PM (#6835192)
I use make. You can see my typical setup for Node packages on GitHub, for example: https://github.com/jaredhanson/locomotive
Re:Eliminating Code Smell with Grunt by jayferd on Monday December 02, 2013 @11:28AM (#6834601)
I use make.
Re:Eliminating Code Smell with Grunt by brandonbloom on Monday December 02, 2013 @11:51AM (#6834755)
I generally prefer Make as well and I even made the case for Make when Grunt.js was first announced [1]. That said, I did use Grunt on a recent project and it worked out reasonably well. For myself, I'd prefer to keep using Make, but for many teams, Grunt is a reasonable choice.

I chose Grunt because Make generally requires a lot more background knowledge and ongoing discipline. Most Grunt tasks are configured by relatively constrained JSON data, so it's pretty hard for non-experts to muck it up unless they need to write a custom task. A Makefile would have created much greater education burden for me. That's particularly a concern when the team's Make/shell expert has time-limited involvement with the project.

[1]: https://news.ycombinator.com/item?id=3777393

Re:Eliminating Code Smell with Grunt by chadly on Monday December 02, 2013 @11:46AM (#6834723)
I find having a "standard" way to run tasks enormously beneficial especially when working with developers cross-platform. Whatever OS you are running, just grunt and all is well. :)
Re:Eliminating Code Smell with Grunt by dugmartin on Monday December 02, 2013 @10:48AM (#6834336)
It makes sense when you use it with grunt-contrib-watch. Then you just keep it running as you are developing and listen for the error "ding" after a save.
Re:Eliminating Code Smell with Grunt by jaredhanson on Monday December 02, 2013 @10:53AM (#6834366)
Actually, no. It's very easy to run a watcher which executes any command (like say jshint itself).