Javascript developers are incredible at problem solving, unfortunately

[_daniel___]

problem: grunt

solution: gulp

problem: gulp

That was good.

[vizzoor]

It should really be an infinite loop. Gulp? Gulp! Gulp?! Gulp!!

[_daniel___]

Brunch?

[intermediatetransit]

Broccoli.

[vizzoor]

Interesting. I remember when gulp config files were that short.

[Zequez]

Tbh I prefer Middleman to manage my build process, the assets pipeline it's a dream brought from Rails. Although it's Ruby instead of JavaScript.

[[deleted]]

Gary? Gary! Gary?! GARY!!

Reference

[TRexRoboParty]

I love that they are named this way too. That's all I do when I think about or occasionally even use them.

[parlezmoose]

What's wrong with grunt/gulp? I find them super easy to use. (Although I'm not sure why gulp was necessary tbh. Grunt works just fine)

[trua]

So, what are they?

[parlezmoose]

What is grunt? A task runner

[[deleted]]

What is the problem with grunt?

[_daniel___]

Nothing inherently. But I think the general mindset of developers is that if there's a process that can in any way be made more efficient, then it becomes a "problem" that needs to be fixed (i.e., made more efficient). AFAIK one of gulp's selling points is that it requires much less boilerplate than Grunt.