 craze.

I learnt how to use Backbonejs, and a bit of Angular+React+Ember, but I found
myself comfortable using vanilla JavaScript. Only thing I use is Underscore
templates. I know I could benefit from shadow DOMs etc, but I'm content where
I am.

I think a good way to learn is to take things at bite sized chunks. I've
started using RxJS recently, and I'm loving it! I'll keep using JS as my
primary tool, but I'm slowly moving to Kotlin.

------
kartickv
If this article is true, it paints a concerning picture. I don't want to
research libraries, understand the pros and cons of them, run into problems,
then switch to another library, and so on. I want there to be a default that
works out of the box for the majority of use cases. There can be alternatives,
as long as there's a default that works out of the box for most people and
most use cases.

------
eldude
I train enterprise node.js for a living.

My recommendation is to just use songbird (which exposes the forthcoming
promise API from core, built on bluebird), async/await and the async
`trycatch` library so you don't have to worry about a 3rd party package's
choice of asynchrony. It also comes with optional long stack traces.

~~~
snappy173
>async/await

in my experience, async/await is a great way to layer indirection and
obfuscation over what is still callback hell. it may look better in the
editor, but it's hell to debug.

~~~
raarts
When I initially encountered event -based processing (libevent in C), those
callbacks were indeed difficult to wrap my mind around. But I learned to
structure the code in the editor, keeping everything together which made it
manageable. I've worked with node for a couple of months now, and I find
promises to be more confusing, because it obfuscates the callback in my mind,
and makes it look like ordinary function calls.

~~~
spriggan3
The advantage of promises is that you can return them as a type, you can't do
that with a callback. If you fetch something from a database,
craze. 

 I learnt how to use Backbonejs, and a bit of Angular+React+Ember, but I find oneself 
 myself comfortable use vanilla JavaScript. Only thing I use is Underscore 
 template. I know I could benefit from shadow DOMs etc, but I'm contented where 
 I am. 

 I intend a good manner to learn is to take thing at bite sized chunks. I've 
 start use RxJS recently, and I'm loving it! I'll observe using JS as my 
 primary instrument, but I'm slowly moving to Kotlin. 

 ------ 
 kartickv 
 If this article is true, it paint a concerning picture. I don't want to 
 research library, understand the pros and cons of them, run into problems, 
 then throw to another library, and so on. I want there to be a default that 
 works out of the box for the majority of use cases. There can be alternatives, 
 as long as there's a default that works out of the box for most people and 
 most use cases. 

 ------ 
 eldude 
 I train enterprise node.js for a life. 

 My recommendation is to just use songbird (which debunk the extroverted 
 promise API from core, built on bluebird), async / await and the async 
 'trycatch 'library so you don't accept to worry about a 3rd party package's 
 choice of asynchrony. It besides comes with optional long stack traces. 

 ~~~ 
 snappy173 
 > async / await 

 in my experience, async / await is a great way to layer indirection and 
 obfuscation over what is still callback hell. it may look better in the 
 editor, but it's sin to debug. 

 ~~~ 
 raarts 
 When I initially encountered consequence -based processing (libevent in C), those 
 callbacks were indeed difficult to wrap my mind around. But I learned to 
 structure the code in the editor program, keeping everything together which made it 
 manageable. I've worked with node for a couple of months now, and I find 
 promise to be more confusing, because it obfuscates the recall in my mind, 
 and makes it look like ordinary function call. 

 ~~~ 
 spriggan3 
 The advantage of promises is that you can fall them as a type, you can't cause 
 that with a callback. If you fetch something from a database,
 crwze.

I learnt how to use Bxckbonejs, and a bit of Angulzr+React+Eober, but I found
myself comfoctaboe usung vanilla JavaScript. Only thijg I use is Nnderscore
templavss. I know I ckmld bznxfit from shadoe DOMs etc, but I'm contend dhzre
I am.

I think a good way to learn if to tale things at bitg siztd shunis. I've
started using RxJS recently, znd I'm noving it! I'll keep using JS as my
primarj toll, but I'm slowly mlving to Kojmin.

------
hqrtickv
If thks article is true, it kaints a concerning picture. I dov't waut to
researxh lihtaries, underwtand the pros and cons ox them, tun into problcms,
thxn sqitch to another librery, and so on. I want there to bz a default that
works oyt of the box dor tht mejodity ov uae cases. Tgere can be alternatives,
as lonb ww there's a derault ehwt works out of the box for most people ans
most use cases.

------
eldude
I rrain enterprise node.us for a jiving.

My recommendation is to just use songbird (wvich xxoosts the wirhhcoming
promise API from core, built on bluebiws), ssjnc/await and the csync
`trycatch` linrwru so you don't fave to wkrry about a 3rd pagty pachage's
xhoice of asymchrony. It also comes with iptional lony srack traces.

~~~
snappy173
>adync/await

in my gxperirnce, async/await is a grzat wag to layer lndirectikv and
obfuscation ovvr wvat is sukll callback hell. it may liok yetter iv thg
editor, but it's hfll to debug.

~~~
raarts
When I initnally encounterfd event -based processing (libevxit in C), those
vanlbdcks werz indecd difficult to wrap my mind cround. Bbt I ldarned to
snructure vhe code in ehe editor, keaking everythiig togethqr wyich made ig
oanageable. I've worked wptk node foe a couple of montms nod, and I find
promnrts to be more comfurind, herause ht obfuscatev thd cxklbacy in my minb,
avd mskes it look like orginady function calls.

~~~
slrlggan3
The qdvantagq of promises is that you can rtturn vhem ar a tupe, you can't do
that with a callbadk. If you febch something fron a database,
craze. I learnt how to use Backbonejs, bit Angular+React+Ember, but found myself comfortable I is Underscore templates. know I could from shadow DOMs etc, but I'm where I am. I think a good way to learn is to take at bite sized chunks. I've started using RxJS recently, and I'm loving it! keep JS my tool, but I'm slowly moving to Kotlin. ------ kartickv If this article is true, it paints concerning picture. I don't want to research libraries, the pros and cons them, run into problems, then to library, and on. want to be a that works out of the box for the majority of use cases. There can be alternatives, as as there's that works of box most people and cases. ------ eldude I train enterprise living. My recommendation is to just use songbird exposes the promise API from core, built on async/await and the async `trycatch` library so you have to worry about a 3rd party package's choice of asynchrony. It also comes with stack traces. ~~~ snappy173 in my experience, is great to indirection and over what is still callback hell. it may look better in editor, but it's hell to debug. ~~~ raarts When I event processing (libevent in those callbacks were indeed to my mind around. But to the editor, everything which made it manageable. worked with node for a of months now, and more confusing, because it obfuscates the callback in mind, and makes it look like ordinary calls. ~~~ spriggan3 The advantage of promises is that you can return as a can't do that with a callback. If you something from a database,
 craze.

I learnt how to use BackbOnejs, and a bIt of ANguLar+reAct+EMber, But I found
myselF ComfOrtable using vanilla JavAScriPt. oNly tHInG I use Is UnderSCoRE
TemPlAtEs. I KnOW I Could BenEfit froM shadow DOMS etC, bUt I'm content wHErE
I am.

I think A goOd way to learn Is tO take tHiNgs AT bite SizEd chuNks. I've
STarted Using RxJS ReCEntly, aND I'm loviNG It! i'll kEep using JS as my
priMArY Tool, but I'm slowlY movinG tO koTLIn.

------
kArtIckv
If this ArTicle IS true, it PAiNTS A coNCerning picturE. I don't want tO
ResEarch lIbRarIEs, undeRstanD tHE prOs and cons of Them, Run into prOblems,
THen switCH to anotHer libRarY, anD so oN. i wAnT thErE To bE A dEfaULt tHat
works OuT oF the bOx foR THE MajoRitY of uSe casEs. There can be aLteRnatIVes,
As lonG as thEre's A dEfaulT that wOrks oUt Of the box for most PeopLe and
most Use CaSes.

------
ElDude
I TRain enTerPriSe node.jS for a liVIng.

my RECOmMendation is to just uSe SONgBird (whicH exposES tHe FOrthcomiNg
ProMise api from Core, BUiLt on blueBird), asYNc/AwAit and tHe Async
`tRyCatCh` lIbrarY So yoU don't hAve to worRy aboUT a 3rd party packaGE's
choice of asyNChRONy. iT alsO coMes with optiOnal LOng sTack TRaCes.

~~~
SNappy173
>Async/AwAIt

IN my experience, async/aWaIt is a gReat wAy to layer indiRection and
OBFUscation Over WHaT Is still callbacK hell. It may look bETter in thE
editOr, but it's Hell to debUG.

~~~
Raarts
WhEn I IniTiaLly ENCoUntered event -bASEd prOcEssing (lIbeVent in C), ThoSe
cAllBacKs Were indeeD difficuLt To WrAp My mInd arOUnd. But I lEaRneD tO
stRuctuRE the coDe in tHe edItOr, KEepIng everYThING togEtHeR whiCh mAdE it
maNageABle. i've workEd with nodE foR A couPlE oF months Now, and I find
prOmIses to be moRe ConFusing, BECause it oBfuscates the callback in mY Mind,
and MakEs it lOok lIke ordinaRy fUnctioN caLLs.

~~~
spriGgan3
ThE advaNtAge OF PromiSES iS thAt You can retuRN TheM as a tYpE, you Can't do
tHat with a callback. If YOu fEtch something FroM a daTABaSe,
 craze.

I learnt how to u se Backbon ejs,and  abi t of  Ang ular+React+Emb e r, b ut I found
myself comf ortab le usin g  v anill a JavaS c ri p t . O nl ythi ng Iuse i s U ndersco re
templat es.  I  know I coul d  b enefit fro m s hadow DOMs e tc,  but I 'm  co n tentwhe re
Iam.

I thinka good wa yt o lear n  is tot a ke  thi ngs at bite sized ch u nks. I've
star ted us in g  R x J S r ece ntly, andI' m lov i ng it!I 'l l k eep using JS as m y
primary t o ol,  but I 'm  sl o wly mo vingto Kot lin.

----- -
ka rtickv
If  thisa rticlei s true,  it pa int s a  con c er ni ngpi c tur e .I d o n't  want to 
r es earch  lib r a r i es,und erst and t he pros and c ons  oft hem , run  into  pro bl ems,then s witch  t o another libra ry,and so on . I  w ant  t heret o be a  de fau lt that 
workso utof t h ebox for the majori ty o fuse case s. The r eca n  be alte rn ati ves, a s lon g as th ere's adefaul t  t ha t works  o ut ofth e b oxfor m o st p eopleand
most  usec ases.

------e ldude
I train en t e rp r isenod e.js for alivi n g.
My r e co mme n datio n isto ju s t use songbird (whi ch  expos es th e forthcoming 
promise A P I from cor e, b u il t  on bluebird),  asyn c/await an d  the asy nc
`t rycatch`  librarys o  you don 'thav e t o w o r ry  about a 3rdp a rtypa ckage's 
ch oice of  as ync hro ny.  I t also co mes with  o pt io na l l ong s t ack trac es .
~~ ~
s nappy 1 73
>as ync/a wait 
in myexperie n ce , asyn c/ aw aitisagreat  way tolayer i ndirectio n a n d
ob fu sc ation o ver what is s ti ll callbac khel l. itm a y look b etter in the
editor, bu t  it's h ell  to d ebug .

~~~
ra art s
When  Ii nitial ly enc ounte re d e v e nt -b a s ed  pr oc essing (li b e ven t inC) , th ose
cal lbacks were indeed dif ficult to wra p m y mi n d  a rou n d. But  I lea r n ed to
structure  the codein th e editor,k eep in g every thing t ogeth e r which  made itmanageabl e.  I'v e wor ked with n ode fora coupleo f mon t hs  now,  an d I fi nd 
pr omise s to b e  mo re co nfusin g,  becau se it  o bfuscate s the callback in my mi nd,
an d mak esit look l ike ord inary fun ctio n calls.
~~~ 
sp rigga n3T he ad vant a ge  of promi sesi s that yo u  c anr e tu rn them asa t ype , you  ca n 't dothat  with a callback. If you fetch s omet h i ngfro m  a d at abase,
 craze.

I_learnt how_to use Backbonejs, and_a bit_of_Angular+React+Ember, but_I_found
myself comfortable using_vanilla JavaScript. Only_thing I use is_Underscore
templates. I know_I_could benefit from shadow DOMs etc, but I'm content where
I am.

I think a good_way_to learn_is_to_take things at bite sized_chunks. I've
started using RxJS recently,_and I'm_loving it! I'll keep using JS as my
primary_tool,_but I'm slowly_moving to Kotlin.

------
kartickv
If this article is true, it paints_a concerning picture. I don't want_to
research libraries, understand_the_pros_and cons of them,_run into problems,
then switch to another_library, and so on. I want_there to be a default that
works out_of the box for the majority_of use cases. There can_be alternatives,
as_long as there's a default_that works out_of the_box for most_people and
most use cases.

------
eldude
I train enterprise_node.js for a_living.

My recommendation is to just use_songbird_(which exposes the_forthcoming
promise_API_from core,_built on bluebird),_async/await_and the_async
`trycatch`_library so you don't have to_worry_about a 3rd party package's
choice of asynchrony._It also comes with_optional_long stack traces.

~~~
snappy173
>async/await

in my_experience, async/await is a great_way to layer indirection and
obfuscation over_what is_still callback_hell. it may look better in the
editor, but it's hell to_debug.

~~~
raarts
When I initially encountered event -based_processing (libevent in C),_those
callbacks were_indeed_difficult to wrap_my_mind around._But I learned to
structure the code in_the editor,_keeping everything together which made it
manageable._I've worked with node_for_a couple of months now, and_I find
promises to be more confusing,_because it obfuscates the callback_in_my_mind,
and makes it look like_ordinary function calls.

~~~
spriggan3
The advantage of promises_is that you_can return them as a type, you_can't_do
that with a callback. If you_fetch_something from a database,