I want to note that this headline is a wonderfully hilarious if read without js-programmer context.
Broccoli, the laxative your JS needs.
No more `grunt watch` – faster builds with the Broccoli asset pipeline
21–30 of 59 posts
Re: No more `grunt watch` – faster builds with the Broccoli asset pipeline
#22This is slightly related and I don't want to sound like I'm trying steal its thunder, because this looks really cool. I work on the asset pipeline that comes with the Dart SDK. It has many of the same principles as these. Any transformation step can read in many input files and produce many output files. The built-in dev server tracks the entire asset dependency graph and only rebuilds the assets that are dirtied by…
Why can't Dart reuse (or provide) a tool that also works for things other than Dart?
Why does every language need to have its own everything unique to itself?
Re: No more `grunt watch` – faster builds with the Broccoli asset pipeline
#23Earlier quoted context omitted.
Broccoli is just one of those words that never looks spelt correctly, even when it is. Might I suggest lumber.js, considering it's all about trees.
Broccoli looks like little trees. I wanted them to be called `Brocfile`s. Who's with me?
I like the Broccoli name quite a bit (and the whole concept and implementation - great job Jo!), but I also prefer `Brocfile` to `Broccolifile`. Does that make me a broccoliphile against broccolifiles?
Re: No more `grunt watch` – faster builds with the Broccoli asset pipeline
#24This looks like a solid project.
I want to mention mincer[1], which I have used in the past for compiling assets, and it has been an entirely painless process. Definitely take a look at it as an alternative, which has been around longer and has seen assistance from the folks behind sprockets[2] (according to the README) for creating a similar API.
1. https://github.com/nodeca/mincer 2. https://github.com/sstephenson/sprockets
Re: No more `grunt watch` – faster builds with the Broccoli asset pipeline
#25Earlier quoted context omitted.
Broccoli looks like little trees. I wanted them to be called `Brocfile`s. Who's with me?
I like the Broccoli name quite a bit (and the whole concept and implementation - great job Jo!), but I also prefer `Brocfile` to `Broccolifile`. Does that make me a broccoliphile against broccolifiles?
I think you mean phobe
Re: No more `grunt watch` – faster builds with the Broccoli asset pipeline
#26Not often I see tools announced with such a thoroughly researched article. Great stuff! I guess the problem these build tools are facing is the amount that people have invested in Grunt. There are just /so/ many grunt tasks at this point.
Can you give some examples of your Grunt tasks?
Re: No more `grunt watch` – faster builds with the Broccoli asset pipeline
#27Earlier quoted context omitted.
I also wonder how it compares to Gulp (mainly in terms of performance in practice). I've just started to use Gulp, migrating away from Sprockets and so far it has been a joy.
fast builds isn't the entire broccoli offering, I would trade slow builds for accurate consistent and durable builds, amazingly with broccoli I get both. I actually do not believe grunt/gulp vs broccoli makes terribly much sense to compare as broccoli aims to be a accurate/stable/fast build pipeline, it does not aim to replace your task runner. It's primary goal is to be the best possible build pipeline, and should b…
[deleted]
Re: No more `grunt watch` – faster builds with the Broccoli asset pipeline
#28What's the difference between a build tool and a task runner?
Re: No more `grunt watch` – faster builds with the Broccoli asset pipeline
#29Not often I see tools announced with such a thoroughly researched article. Great stuff! I guess the problem these build tools are facing is the amount that people have invested in Grunt. There are just /so/ many grunt tasks at this point.
Yep- a search on npmjs shows not quite a dozen tasks for Broccoli while Grunt has hundreds of results. Not that quantity necessarily == quality but when it comes to a task runner, I need to, you know, run tasks. Definitely awesome that people are trying to optimize in the devops space but just not sure I could be convinced to switch to something that isn't at least somewhat mature.
I think the trouble comes in that 3/4 or more of Grunt plugins are things that really have very little reason to be plugins in the first place. Given how flexible node really is, and how npm tasks work, I'm more an more inclined to simply having a ./scripts/ directory with a file per task registered in package.json, so I can simply `npm run taskname` and have it correlate to `./scripts/taskname.js|coffee` ...
With node.js as a host environment, it's easy enough to do pretty much whatever you want as a script/task, and is pretty much cross platform, and works well. Shell scripts come close, but ignore the elephant in the room (Windows).
For the record, I'm biased as all hell, like node.js and JavaScript in general.
Re: No more `grunt watch` – faster builds with the Broccoli asset pipeline
#30Earlier quoted context omitted.
I like the Broccoli name quite a bit (and the whole concept and implementation - great job Jo!), but I also prefer `Brocfile` to `Broccolifile`. Does that make me a broccoliphile against broccolifiles?
I think you mean phobe
Actually, both a broccoliphile and a broccolifilephobe.