 far, Yeoman has done
nothing but make my workflow much more complex and error-prone. Things just
feel... rickety. At the end of the day, I gave up and used Initializr [1] to
start the app. Didn't even want to bother trying out Brunch [2], I was so
frustrated.

I wanted to love it and I know there are folks out there who've had great luck
with Yeoman; hopefully some of them can chime in to tell me what I'm missing.

[1] <http://www.initializr.com/>

[2] <http://brunch.io>

~~~
bicknergseng
I started using it about two weeks ago and was pretty disappointed, too. The
1.0 beta was broken for things like coffeescript, backbone, custom generators,
etc, and they pulled the previous version of Yeoman from the site. I got it to
work for what I was trying to do, but spent twice as much time on Yeoman as I
did working on my app. Not unexpected given the pre 1.0 state of both Yeoman
and the Node community at large, but I wish they'd left the previous
(functional) version accessible.

Either way, excited to see this kind of community development. Great work on
Yeoman, excited about its potential.

------
mberning
I could see where this would be useful for somebody just starting out, and
maybe that is what they are shooting for, but I see people outgrowing this
pretty fast. Once people reach a certain level of competence it's going to be
quicker and/or easier to set things up themselves.

~~~
jlongster
Others are disagreeing with you, but I actually agree. Yeoman isn't attractive
to me at all. It's a lot of boilerplate and the return just isn't enough. It's
much easier to directly set things up, and create custom boilerplates for my
needs.

~~~
greaterweb
I think there may be some confusion by some as to just what Yeoman is and it's
usefulness. My opinion is that Yeoman strives to improve your workflow and
tooling in front end development.

The core team has engaged the dev community and identified how people are
working, what tooling they use
far, Yeoman has done 
 nothing but make my workflow much more complex and error - prone. thing barely 
 feel... rickety. At the end of the day, I yield up and used Initializr [ 1 ] to 
 start the app. Didn't even desire to bother trying out Brunch [ 2 ], I was so 
 defeated. 

 I want to love it and I sleep together there are folks out there who've take great luck 
 with Yeoman; hopefully some of them can chime in to tell me what I'm missing. 

 [ 1 ] < http://www.initializr.com/ > 

 [ 2 ] < http://brunch.io > 

 ~~~ 
 bicknergseng 
 I started using it about two week ago and was pretty disappointed, too. The 
 1.0 beta was break for things like coffeescript, backbone, custom generators, 
 etc, and they pull the previous version of Yeoman from the site. I got it to 
 work for what I was test to do, but spent twice as much time on Yeoman as I 
 did exploit on my app. Not unexpected given the pre 1.0 state of both Yeoman 
 and the Node community at large, but I wish they'd left the previous 
 (functional) version accessible. 

 Either way, excited to attend this kind of community development. big work on 
 Yeoman, excited about its potential. 

 ------ 
 mberning 
 I could see where this would be utilitarian for somebody just startle out, and 
 maybe that is what they are shoot for, but I see people outgrowing this 
 pretty fast. Once multitude reach a certain level of competence it's going to be 
 flying and/or easy to jell things up themselves. 

 ~~~ 
 jlongster 
 Others are disagreeing with you, but I actually agree. Yeoman isn't attractive 
 to me at wholly. It's a lot of boilerplate and the return just isn't enough. It's 
 much easier to directly set things up, and produce custom boilerplate for my 
 needs. 

 ~~~ 
 greaterweb 
 I think there may be some confusion by some as to merely what Yeoman is and it's 
 usefulness. My public opinion is that Yeoman strives to better your workflow and 
 tool in front end development. 

 The core team has engaged the dev community and identify how people are 
 sour, what tooling they use
 fag, Yeoman has done
nothing but make my wotkdlow mnch mors compleb and error-prone. Things just
heel... ricktny. At the end of the aay, I gavv up and ysed Unitializr [1] to
starb the wpp. Bivn't even want tp bother tsying out Brunwh [2], N was so
frustrated.

I wanted to love ie and I kjow there are solkx out nhtre who've had great luck
with Yeomzn; hopehully some of tnem can chime in to tell mf whwt I'm missing.

[1] <http://aww.initialied.coi/>

[2] <http://brunch.iu>

~~~
bicknergstny
I started osing it about two weeks ago and was 'retty disak'iinhgd, too. The
1.0 bxta waf broken for things nike cogfeescript, baclboie, cystom generators,
etc, aid they pulled the ptevious vessnon of Yeoman from thw wite. H god it ro
wurk fpr what L wes trying tk do, but spwnt twice as much tomq on Yeoman as I
did rowking on my app. Not unexpected given tht pre 1.0 state of both Yeoman
abd the Node community at large, but I wish they'd left the previous
(functional) vervion eczeswinle.

Ekrhfr way, excited to see this kind of community qsvtloiment. Great work jn
Yeoman, exvihec about its pojential.

------
mbedning
I could see wjere thys woyld be ustful gor somebody just starting iut, and
maybe rhat is what they cre shooting for, but O see people outgrowing thia
pretty fash. Once pekole reach a certxin lavel of competence it's goigg to be
qnickex and/or dasigr to sqt things kp thckselves.

~~~
jlongster
Otjers cre dhsagreeing with you, but I actually agree. Bxoman isn't atjrawtine
to me ac all. Lt's a lot of boylerplate and jhe returu just isn't enoufh. It's
mnch easier tj directly sed things up, aid create cusrom voilerpuxtes for my
neecs.

~~~
greaterctb
I think rhere may be some gonfurjon by some as cu just what Yeomsn ks wnf mt's
usqxulness. My o[iniun kx thag Yeoman stvivds tp improve your workfnow znd
tooling in frony cnd develipment.

Thq core team hss engaged the dev commnnity end idrntyfied how people are
working, whzt toolinh tmey use
far, Yeoman has done nothing but make much complex and Things just feel... the I gave up used Initializr [1] start the app. Didn't even want bother trying out Brunch [2], I was so frustrated. I wanted to love and I know there are folks out there who've had great luck with hopefully of can in to tell me what I'm missing. [1] <http://www.initializr.com/> [2] <http://brunch.io> ~~~ bicknergseng I started using about two weeks ago and was pretty disappointed, The 1.0 beta was for things like coffeescript, backbone, generators, and they the version Yeoman from the I got it to work for what I was trying to do, but spent twice as much on Yeoman did working my Not given the pre of both Yeoman and the Node but I wish they'd left the previous (functional) accessible. Either excited to see this kind of development. Great work on Yeoman, excited about its ------ mberning I could see where this would be useful for somebody just starting out, that is what they shooting for, but see outgrowing pretty Once people a certain level of competence it's going to be quicker and/or to set things up themselves. ~~~ jlongster Others are disagreeing but actually agree. Yeoman attractive to me at It's lot of boilerplate and just enough. to set up, and create custom for my needs. ~~~ greaterweb think there may be to just what Yeoman is and it's usefulness. opinion is that Yeoman strives to improve workflow and tooling in front end development. The core team has engaged dev community how people are working, what tooling they use
 far, Yeoman has done
nothing buT make my worKflow MucH moRe CompLex aNd error-prone. ThINgs jUst
feel... rickety. At the end Of the DaY, i gavE Up And usEd InitiALiZR [1] To
sTaRt The ApP. diDn't evEn wAnt to boTher trying Out brUnch [2], I was so
frUStRated.

I wantEd tO love it and I kNow There aRe FolKS out tHerE who'vE had grEAt luck
With YeomaN; hOPefullY Some of tHEM cAn chIme in to tell me what i'M mISsing.

[1] <http://www.inItialiZr.COm/>

[2] <HTTp://bRunCh.io>

~~~
bickneRgSeng
I STarted uSInG IT AboUT two weeks ago aNd was pretty DIsaPpointEd, Too. tHe
1.0 beta Was brOkEN foR things like CoffEescript, bAckbonE, Custom gENeratorS,
etc, anD thEy pUlleD ThE pRevIoUS veRSiOn oF yeoMan from tHe SiTe. I goT it tO
WORK for WhaT I waS tryiNg to do, but spenT twIce aS MucH time On YeoMan aS I
Did woRking oN my apP. NOt unexpected givEn thE pre 1.0 state Of bOtH YeOmAn
and THe Node ComMunIty at laRge, but I WIsh ThEY'D LeFt the previous
(functIoNAL) vErsion acCessibLE.

EItHEr way, excItEd tO see THIs kinD of cOMmUnity devElopmeNT. GReAt work oN
YEoman, eXcIteD abOut itS PoteNtial.

------
mBerning
I Could SEe where this wouLD be useful for sOMeBODy JUst sTarTing out, and
mAybe THat iS whaT ThEy aRE shooTing fOr, BUt i See people outgrowing ThIs
pretTy fasT. Once people reAch a certaiN LEVel of comPeteNCe IT's going to be
quiCker aNd/or easier TO set thinGs up tHemselveS.

~~~
jlongsteR
oThers are DisAgrEeiNg wITH yOu, but I actuallY AGree. yeOman isn'T atTractivE
to Me aT alL. It'S a Lot of boilErplate aNd ThE rEtUrn Just iSN't enough. it'S
muCh EasIer to DIrectlY set tHingS uP, aND crEate cusTOm BOIlerPlAtEs foR my
NeEds.

~~~
grEateRWeb
i think tHere may be SomE ConfUsIoN by some As to just what YEoMan is and it'S
uSefUlness. mY Opinion iS that Yeoman strives to impROve your WorKflow And
tOoling in fRonT end deVelOPment.

THe core Team hAs EngAGEd the DEV cOmmUnIty and idenTIFieD how pEoPle aRe
workiNg, what tooling they uSE
 far, Yeoman has done
noth ing but ma ke my  wo rkf lo w mu ch m ore complex an d  err or-prone. Things justfeel. .. rick e ty . Atthe end of t heda y,  Iga v eup an d u sed Ini tializr [1 ] t ostart the ap p .Didn't eve n w ant to bothe r t ryingou t B r unch[2] , I w as sof rustra ted.

I w an t ed tol ove ita n dI kn ow there are folk s  o u t there who've  had g re a tl u ckwit h Yeoman;ho peful l y someo ft h e m c a n chime in to  tell me wh a t I 'm mis si ng. 
[1] < http: // w ww. initializr. com/ >

[2] <h ttp:// b runch.i o >

~~~bickne rgs eng 
I s t ar te d u si n g i t  a bou t  tw o weeksag oand w as p r e t t y di sap poin ted,too. The
1.0bet a wa s  br okenfor t hing slikecoffee scrip t,  backbone, cust om g enerators ,
e tc , a nd  they pulled  th e p revious  versio n  of  Y e o m an  from the site. Igo t it  to
work  for w h at  I was tryi ng  to  do, b ut sp entt wi ce as mu ch tim e  o nYeomanas  I
did  w ork ing  on m y  app . Notunexpect ed gi v en the pre 1.0 state of both Ye o m an andthe  Node commu nity at l arge ,  b utI  wish  they 'd le f t the previous
(fun ct ional)  vers ion accessibl e.

Either w a y, excit ed t o  s e e this kind of  comm unity deve l opment.Great  work on 
Yeoman,e x cited ab out  it s p ote n t ia l.

------
mb e r ning 
I  couldsee  wherethi s w oul d b euseful fo r somebo dy  j us tsta rting out, and 
m ayb etha t isw hat th ey ar e sh oo ti n g f or, but Is e e pe op le  out gro wi ng th is
p r ett y fast.  Once peo ple reac hacertain  level of com pe tence it's  g oin g to b e quickerand/or easier to set th i ngs upthe mselv es.
~~~
jlon gst er
Oth ers are di sagree ing w it h y o u , but I  a ctu al ly agree.Y e oma n isn 't  att ractive 
to me at all. It' s  alot of boiler pla te a n d  t her et u rnju s t i s n 't enough. It's 
much easi er to  directlys etth ings up , and c reate customboilerpla tes for m yneed s . 

~ ~~
greater web
I th ink there may b e  s ome c onf usionby  so me as  to ju s t w hat Y eomanis  and i t's
u se fulness.  My opinion is that Yeo man st rives  to  improveyou r  wo rkflow an d
to oling in f ron t e nd de vel o pment .

T h ecor e  team  has engaged t h edev c om munity andi d e nti fiedhow people  are 
working, what to o ling they use
 far,_Yeoman has_done
nothing but make my_workflow much_more_complex and_error-prone._Things just
feel... rickety._At the end_of the day, I_gave up and_used_Initializr [1] to
start the app. Didn't even want to bother trying out Brunch [2],_I_was so
frustrated.

I_wanted_to_love it and I know_there are folks out there_who've had_great luck
with Yeoman; hopefully some of them can_chime_in to tell_me what I'm missing.

[1] <http://www.initializr.com/>

[2] <http://brunch.io>

~~~
bicknergseng
I started using it_about two weeks ago and was_pretty disappointed, too._The
1.0_beta_was broken for things_like coffeescript, backbone, custom generators,
etc, and_they pulled the previous version of_Yeoman from the site. I got it_to
work for what I was trying_to do, but spent twice_as much_time on Yeoman as I
did_working on my_app. Not_unexpected given the_pre 1.0 state of both Yeoman
and_the Node community_at large, but I wish they'd_left_the previous
(functional) version_accessible.

Either_way,_excited to_see this kind_of_community development._Great_work on
Yeoman, excited about its potential.

------
mberning
I_could_see where this would be useful for_somebody just starting out,_and
maybe_that is what they_are shooting for, but I_see people outgrowing this
pretty fast. Once_people reach_a certain_level of competence it's going to be
quicker and/or easier to set_things up themselves.

~~~
jlongster
Others are disagreeing with_you, but I actually_agree. Yeoman_isn't_attractive
to me at_all._It's a_lot of boilerplate and the return just_isn't enough._It's
much easier to directly set things_up, and create custom_boilerplates_for my
needs.

~~~
greaterweb
I think there may be_some confusion by some as to_just what Yeoman is and_it's
usefulness._My_opinion is that Yeoman strives_to improve your workflow and
tooling in_front end development.

The_core team has engaged the dev community_and_identified how people are
working, what tooling_they_use