Yeoman and Brunch #408
Comments
This is my subjective opinion from the position of web application developer. Updated at November 24 Pros of yeoman:
Conceptual differences:
Developing the “free market” topic, I believe existence of Yeoman is a potentially good thing, because it brings competition to the board. Yeoman will become better, brunch will become better. |
Shouldn't you add also the language used in the conceptual difference? ( I wonder, if |
I don’t think user really cares in which language his tool is written unless he contributes to it. After all, both brunch and yeoman support compiling both coffeescripts and javascripts etc. Nothing stops yeoman from using brunch as a backend instead of yeoman (brunch is compiled to js, after all), but I think they’ve picked Grunt instead because of its ecosystem. But from the view of contributor to both projects, the big coding difference between projects:
|
I can't predict what Brunch will look like with Bower, but along those same lines perhaps it is feasible to have some CLI sugar for adding brunch plugins. Something like: "brunch install livereload" = "npm install livereload-brunch --save"? |
@eriwen good idea! |
The only thing I see in Yeoman I'd like is an automated appcache manifest generator. |
@KyleAMathews you mean like appcache-brunch? |
No -- it looks like they're using confess.js to do the actual manifest generation - yeoman/yeoman#21 |
cool idea. |
Brunch is far more mature because it existed longer. I predict yeoman will fight some of the issues brunch already solves. |
yes true. Brunch is more mature. I tried yeoman, and while it has some fancy things, I don't like how it interferes with the workflow. With brunch, I just create my app under client and point express's Besides, yeoman is based on grunt and js... I'm a coffeescript user and it made a difference to see js instead of cs in the code. |
tUrG0n, yeoman is an opinionated workflow. It's either we love it, or not. |
that's too simple. I don't believe you can generalize this easily. Each has its pros and cons. |
Curious what the status is of bower support. Mentioned as going to be part of 1.5. I see there's a package here: https://github.com/brian-c/bower-brunch but before attempting to use wanted to find out if there was an "officially" supported one |
no bower support, it still does not support stuff for build tools |
gotcha. Thanks for very quick reply btw. Trying to use it manually, and attempting to grok the regex in the joinTo part of config.coffee to filter out (or just include) the *.min.js files... But that's a question for a different forum :-) |
Take another look at brunch/appcache-brunch. It now generates the cache manifest based on the contents of the public directory, and includes a hash in a comment that will invalidate the manifest if—and only if—something changes. |
Been using it on a project for awhile :) It works great. Thanks for the Kyle Mathews Blog: kyle.mathews2000.com/blog On Sat, Jul 13, 2013 at 1:23 PM, David Chambers notifications@github.comwrote:
|
What the difference between Yeoman and Brunch ?
The text was updated successfully, but these errors were encountered: