I would like to request renaming brocollifile.js to brocolli.js. I believe brocollifile.js is too long for a standard build file name. Gruntfile.js always bothered me. Compare it to pom.xml, build.xml, package.json and it feels out of place.
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?
Comments
I would like to request renaming brocollifile.js to brocolli.js. I believe brocollifile.js is too long for a standard build file name. Gruntfile.js always bothered me. Compare it to pom.xml, build.xml, package.json and it feels out of place.
I named it after the `Makefile` pattern, since it contains a build definition. We have `Rakefile`, `Cakefile`, `Gruntfile.js`, etc.
How about "Brocfile.js"?
It's a crummy pattern. broccoli.js FTW!
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?
I think you mean phobe
Actually, both a broccoliphile and a broccolifilephobe.
Gruntfile.js is the same length as package.json.