4 ms·
What does your build process look like? What's the tooling, and how do you invoke it? Just curious about alternatives.
by possibilistic 13y ago
What does your build process look like? What's the tooling, and how do you invoke it? Just curious about alternatives.
- jayferd 13y agoI use make.
- brandonbloom 13y agoI 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 https://news.ycombinator.com/item?id=3777393
- jt009 13y agoDon't give us that BS. Make is braindead simple to use. There's no such thing as a Make/shell expert.
- jaredhanson 13y agoI use make. You can see my typical setup for Node packages on GitHub, for example: https://github.com/jaredhanson/locomotive https://github.com/jaredhanson/locomotive