Yeoman: Modern workflows for modern webapps
1–10 of 77 posts
Re: Yeoman: Modern workflows for modern webapps
#2EDIT – totally missed that this in fact uses Bower for the package managment, so probably couldn't even launch until that was released.
Re: Yeoman: Modern workflows for modern webapps
#3EDIT: Nevermind, I see it is not supported yet, http://yeoman.io/gettingstarted.html Any best guess as to when this will be available?
Re: Yeoman: Modern workflows for modern webapps
#4I've been watching/waiting for Yeoman for quite a while now. I can't help but wonder how much Twitter's Bower pushed you towards launching today. This looks to fit a lot more of the workflow than just package management though and does a lot of the things I'm currently doing myself through a huge mashup of other tools. EDIT – totally missed that this in fact uses Bower for the package managment, so probably couldn't…
Re: Yeoman: Modern workflows for modern webapps
#5How does Yeoman compare, and why should I switch?
I asked this in a previous submission on Grunt, in a thread that talked about Yeoman, but I never got an answer.
[1]: http://brunch.io/
EDIT: It looks like the new FAQ addresses this issue: http://yeoman.io/faq.html > "How does Yeoman differ from tools like Brunch or BBB?" and "How does Yeoman differ from Grunt?". Post left up for other users who are wondering how this compares to Grunt or Brunch.
However, the answer seems a little... underwhelming. Apparently it's "we've made making your own scaffolds easier". Are there any other, unmentioned benefits?
EDIT2: Partial updates as I discover this myself (hope that's okay): one huge advantage is how it uses Bower beneath the surface. No more manual AngularJS/JQuery/other dep upgrading!!
Re: Yeoman: Modern workflows for modern webapps
#6Re: Yeoman: Modern workflows for modern webapps
#7Re: Yeoman: Modern workflows for modern webapps
#8It is written by the same guy who wrote require.js. It probably needs better documentation, but it will be improved over time.