Comment by tristan_juricek | Hacker News Reader

Comment by tristan_juricek | Hacker News Reader

tristan_juricek

edit: I could see this being just a good general approach to development. Like a concrete how-to on doing continuous delivery from day one.

I've even started using grunt with a C++ project I'm working on, and if I make sure that from day one I can start up from a new machine:

   % grunt init

... my life is better.

It's interesting, grunt is a nice "automation layer", as opposed to a build tool. I'm now using it to automate my build setup. Having that extra thing to bring it all together into one command makes it all so much easier.

What makes grunt better than the alternatives?

I am wondering the same thing. I would imagine that if your whole stack (especially build system) is built ontop of javascript you could have a level of meta programming via esprima, but the rest is bla

Grunt is not a great build tool. It's not terrible, either, but it puts too much emphasis on a giant declarative config object.

But Grunt has a huge library of plugins that cover all your build automation needs, and that's made it the de-facto standard for build automation in the JavaScript world.

I'm working on a universal build format that would allow you bring the convenience of Grunt plugins to other tools as well. (I'm fond of Jake, myself.) PM me or follow my Github [1] for more. The first version's going up next week.

[1] https://github.com/jamesshore/

Reply on news.ycombinator.com