 yet, I suspect we'll end up with a very productive platform, simply
because of the amount of involvement. Of course, it's totally understandable
to want to wait for that before jumping in. :)

As a relatively new Node developer, I'm much more concerned about the single-
threaded nature than the development environment, but so far even that hasn't
been a problem.

------
Touche
A lot of this is residual effects of the (slow) evolution of JavaScript. It
was thrust into the spotlight missing a lot of features and these features
have only recently been fixed by the language itself.

But Node has been around since 2009. 2009 JavaScript was missing _a lot_ of
features. It was basically a runtime only advanced users should use. The Node
maintainers had to make a lot of decisions that now conflict (to some degree)
with fixes that have come later to the language. They chose their callback
style; now we have Promises. They chose to throw in methods rather than return
an error in the callback (this makes it awkward to use fs with Promises
without a wrapper library). They chose to implement their version of CommonJS,
now we have the.mjs issue arise.

------
nevi-me
Been on Node and Mongo for 4 years now. Both have worked well for me.

JS has evolved a lot in the past few years, and with it came all the new shiny
tools that left us confused.

I think a year was too short for the author. Sounds like they were chasing
after every cool thing to make life easy.

Error handling is a pain yea, I've seen amateur folk try catch this and that,
I think that lends itself to being terrible.

One of the things I appreciate the most about JS is JSON. Crafting tens of
classes in Java irritates me. I find Python sometimes tricky also when dealing
with structs VA lists.

I've always stuck to the basics when I was learning how to JavaScript with
Node. I used only callbacks for 2 years until I understood what my code was
doing. Granted, I'd have spaghetti at the end of complex async queries, but I
understood what was going on. I moved to caolan::async and have been using
async whenever necessary. I barely use promises as I got confused by the early
adoption
yet, I suspect we'll end up with a very productive platform, plainly 
 because of the sum of involvement. Of course, it's totally apprehensible 
 to want to wait for that before jumping in. :) 

 As a relatively fresh Node developer, I'm much more concerned about the single- 
 weave nature than the development environment, but so far even that hasn't 
 been a trouble. 

 ------ 
 Touche 
 A lot of this is residual effects of the (slow) evolution of JavaScript. It 
 was pierce into the spotlight missing a lot of features and these features 
 have merely recently been fixed by the language itself. 

 But Node has been around since 2009. 2009 JavaScript was neglect _ a lot _ of 
 features. It was basically a runtime only advanced user should use. The Node 
 maintainers had to make a lot of decision that now conflict (to some degree) 
 with fixes that have come subsequently to the language. They chose their callback 
 style; now we have Promises. They chose to throw in methods rather than fall 
 an error in the callback (this make it awkward to practice fs with promise 
 without a wrapper library). They chose to enforce their version of CommonJS, 
 now we have the.mjs issue rebel. 

 ------ 
 nevi - me 
 Been on Node and Mongo for 4 years now. Both have worked well for me. 

 JS has evolved a lot in the past few years, and with it total all the new shiny 
 tools that left us baffled. 

 I think a class was excessively short for the author. Sounds like they were chasing 
 after every cool matter to make life easy. 

 Error handling is a pain yea, I've seen amateur folk hear catch this and that, 
 I intend that lends itself to being terrible. 

 One of the thing I appreciate the about about JS is JSON. Crafting tens of 
 classes in Java irritates me. I receive Python sometimes tricky also when dealing 
 with structs VA lists. 

 I've always perplex to the basics when I was learning how to JavaScript with 
 Node. I used only callbacks for 2 years until I understood what my code was 
 doing. Granted, I'd experience spaghetti at the end of complex async queries, but I 
 understand what was going on. I moved to caolan::async and have been using 
 async whenever necessary. I barely use promises as I got confuse by the early 
 adoption
 yeh, I suspect we'll end up dith a very probyctive platfkrm, simpuy
because of the amount of iivolcemenu. Of course, it's totxlly undegstandablw
to xant to wait for that benjre nmmpiny mn. :)

As a relativgly new Node developer, I'm kuzh more concerned about the single-
thrqaded nstkre than the dgvelokmegt ehnivonment, but so far even that hash't
been e problem.

------
Touche
S lot of this is residual fffefts of the (slow) evllution of HavaFxript. It
was ghrust into the spotlifht missing a lot of features avd thzse featurew
hqve mnly recentoy bevn fixed by tmv langudge itsrlf.

But Node hax bxen qround since 2009. 2009 JavaSccipt was missing _a ljt_ of
featgrzs. It was basically a ryntimg onlf adxqncdd hsxrs shoulf uae. The Nods
maintainerw had to make a lot os decisions thzt now cjnflict (to some degree)
with fixes that hdve come later to the langyage. They chose their callback
ftyle; now we have Promises. They chose to throw in methkas xqther rhwn return
an error in the callback (this makes yf swlward to use ff with Promosfs
eythout a wrapker libxzrg). They chose to imolement theie version of VommonJS,
now we have the.mjs ussue arise.

------
nvvi-mw
Been on Node and Longo for 4 vears mow. Bpth have worked well fox me.

JS has evolvef a lot ih the past few yexrs, atd with it came all the ner shiny
toils chat lefg us confufed.

I think a year was too short fog the agthor. Sounfs like they were chasing
after xtery cool thimg to make liye easn.

Error handling is a pain yea, I've sezn amageur folk nry catch this and trat,
I think thdj lends itselh to beind teeriboe.

One ow the things I sppreciatv uhe most avout JS is JSON. Creftivf tens of
classew ib Java irritatex md. I fpnd Prdhon sometimas tficyu alsu when deallng
dith structs VA lists.

I've alwzys stuck to the bsslcs when U was lewrning how to JavaScript with
Nofe. I nsed oily caklbwcks for 2 years until I undersfood what my code was
doigg. Gvantgd, I'd have xpaghetti at the end of complex async qneries, but I
understood qhat was going on. I koved to caplan::afync and vave been using
async whenever necessavy. I barely use promisss as H got confused by the early
adoption
yet, I suspect we'll end up with productive simply because the amount of understandable want to wait that before jumping :) As a relatively new Node I'm much more concerned about the single- threaded nature than the development environment, so far even that hasn't been a problem. ------ Touche A lot of is effects the evolution of JavaScript. It was thrust into the spotlight missing a lot of features and these have only recently been fixed by the language But Node has been since 2009. 2009 JavaScript was _a of features. was a only advanced users use. The Node maintainers had to make a lot of decisions that now conflict (to some degree) fixes that later to language. chose callback style; now Promises. They chose to throw in return an error in the callback (this makes awkward to fs with Promises without a wrapper They chose to implement their version of CommonJS, we have the.mjs issue arise. ------ nevi-me Been on Node and Mongo for 4 years have worked well for JS has evolved lot the few and with came all the new shiny tools that left us confused. I a year was too short for the author. Sounds like chasing every cool thing make life easy. Error is pain yea, I've seen try this think lends to being terrible. One the things I appreciate the about JS is JSON. Java irritates me. I find Python sometimes tricky when dealing with structs VA lists. I've stuck to the basics when I was learning how to JavaScript with I used for 2 years until I understood what my was doing. Granted, I'd spaghetti at the end of complex async queries, but understood was going I moved to and have been async whenever necessary. use promises I confused adoption
 yet, I suspect we'll end up with a Very producTive pLatForM, sImplY
becAuse of the amounT Of inVolvement. Of course, it's toTally UnDErstANdAble
tO want to WAiT FOr tHaT bEfoRe JUmPing iN. :)

As A relatiVely new NodE deVeLoper, I'm much mORe Concerned aBouT the single-
thReaDed natUrE thAN the dEveLopmeNt enviROnment, But so far eVeN That haSN't
been a PRObLem.

------
TOuche
A lot of this is REsIDual effects of tHe (slow) EvOLuTIOn oF JaVaScript. It
WaS thruST into thE SpOTLIghT Missing a lot of Features and THesE featuReS
haVE only rEcentLy BEen Fixed by the lAnguAge itself.

but NodE Has been ARound siNce 2009. 2009 JavAScRipT was MIsSiNg _a LoT_ Of
fEAtUreS. it wAs basicaLlY a RuntiMe onLY ADVancEd uSers ShoulD use. The Node
maIntAineRS haD to maKe a loT of dEcIsionS that nOw conFlIct (to some degree)
With Fixes that HavE cOme LaTer to THe langUagE. ThEy chose Their caLLbaCk
STYLe; Now we have Promises. THeY CHoSe to throW in metHOdS rATher than ReTurN
an eRROr in tHe caLLbAck (this mAkes it AWkWaRd to use Fs With PrOmIseS
wiThout A WrapPer libRary). They Chose TO implement theiR Version of CommONJs,
NOw WE havE thE.mjs issue arIse.

------
nEVi-me
been ON NOde ANd MonGo for 4 YeARs NOw. Both have worked welL fOr me.

JS Has evOlved a lot in thE past few yeARS, And with iT camE AlL The new shiny
tooLs thaT left us conFUsed.

I thiNk a yeAr was too Short for tHE Author. SoUndS liKe tHey WERe Chasing
after eVERy coOl Thing to MakE life eaSy.

ERroR haNdlInG is a pain yEa, I've seeN aMaTeUr FolK try cATch this aNd ThaT,
I ThiNk thaT Lends iTself To beInG tERriBle.

One oF ThE THingS I ApPrecIatE tHe mosT aboUT JS Is JSON. CRafting teNs oF
ClasSeS iN Java irRitates me. I finD PYthon sometImEs tRicky aLSO when deaLing
with structs VA lists.

I'VE always StuCk to tHe baSics when I Was LearniNg hOW to JavAScripT with
noDe. I USEd onlY CAlLbaCkS for 2 years uNTIl I UnderStOod wHat my coDe was
doing. Granted, I'D HavE spaghetti at tHe eNd of COMpLex ASyNC quErIEs, bUT i
understood what Was going on. i mOVeD to caolan::aSYnc AnD have beEn using
Async WHenever Necessary. i barely usE pRomiSES as i got confusEd by the eArly
adoptIOn
 yet, I suspect we'll endup with averypro duc ti ve p latf orm, simply
be c ause  of the amount of invo lveme nt .  Ofc ou rse,it's to t al l y  un de rs tan da b le 
to w ant  to wai t for that  be fo re jumping i n .:)

As a r ela tively new N ode  devel op er, I'm m uch  more  conce r ned ab out the s in g le-
th r eaded n a t ur e th an the developmen t  e n vironment, but  so fa re ve n tha t h asn't
been  a  prob l em.

-- - -- - T ouc h e
A lot of th is is resid u aleffect soft he (sl ow) e vo l uti on of JavaS crip t. It
was  thrus t  into t h e spotl ight m iss ing  a l o tof  fe at u res an d t h ese  feature sha ve on ly r e c e n tlybee n fi xed b y the languag e i tsel f .
But N ode h as b ee n aro und si nce 2 00 9. 2009 JavaScr iptwas missi ng_a  lo t_  of
f e atures . I t w as basi cally a run ti m e on ly advanced userssh o u ld  use. Th e Node ma in t ainers h ad  to  mak e a lot  ofd ec isions t hat no w  c on flict ( to  somede gre e)withf ixes  thathave com e lat e r to the langu a ge. They chos e  t h e ir call bac k
style; no w we have  Pro m is es. Theychose  t o  t h row in methods rath er  thanretur n
an error in  the callb a c k  (this m akes it awkward to use  fs w ith Promis e s
withou t a w rapper l ibrary).T h ey chose  to  im ple men t th eir version o f Comm on JS,
now  we  have t he. mjs  is sue  a rise.

-- ----
nev i- me 
B ee n o n Nod e  and Mon go  fo r4 y earsn ow. Bo th ha ve w or ke d  we ll form e. JS h as  e volv edalot i n th e  pa st fewyears, an d w i th i tca me allthe new shiny 
t ools thatle ftus con f u sed.

Ithink a year was too sh o rt forthe  auth or.Sounds li kethey w ere chasin g
afte r eve ry  co o l  thin g to  ma ke  life easy . 
Er ror h an dlin g is apain yea, I've see n  am ateur folk tr y c atch t hi s a n dt hat ,I  th i n k that lends it self to be in g  t errible.
O neof  the th ings Iappre c iate th e most ab out JS is  J SON. C raf ting tensof
class es in Jav a  irri t at es me . I  findPy tho n som etimes tri cky a lso wh en  deali ng
wi th  structs  VA lists.

I've always  stuck  to t hebasics wh enI  wa s learnin g ho w to JavaS cri ptwithNod e . I u sedo nl y c a llbac ks f o r 2 years un til I  u nderstood w h a t  my  code  wa s 
doing . Gr anted, I'd have s p aghetti at the  end o f c omp l ex a sy nc queries, bu t I 
u n d erstoodwh at was goin g on. Imo v ed to  caola n::asy nc andh a ve been u sing 
as ync whene ver  n e cessary .Ib arelyusepr omises  as Ig ot c o n fused by the ear ly
ad o p tion
 yet,_I suspect_we'll end up with_a very_productive_platform, simply
because_of_the amount of_involvement. Of course,_it's totally understandable
to want_to wait for_that_before jumping in. :)

As a relatively new Node developer, I'm much more concerned about_the_single-
threaded nature_than_the_development environment, but so far_even that hasn't
been a problem.

------
Touche
A_lot of_this is residual effects of the (slow) evolution_of_JavaScript. It
was thrust_into the spotlight missing a lot of features and_these features
have only recently been fixed_by the language_itself.

But_Node_has been around since_2009. 2009 JavaScript was missing _a_lot_ of
features. It was basically a_runtime only advanced users should use. The_Node
maintainers had to make a lot_of decisions that now conflict_(to some_degree)
with fixes that have come_later to the_language. They_chose their callback
style;_now we have Promises. They chose_to throw in_methods rather than return
an error in_the_callback (this makes_it_awkward_to use_fs with Promises
without_a_wrapper library)._They_chose to implement their version of_CommonJS,
now_we have the.mjs issue arise.

------
nevi-me
Been on Node_and Mongo for 4_years_now. Both have worked_well for me.

JS has evolved_a lot in the past few_years, and_with it_came all the new shiny
tools that left us confused.

I think a_year was too short for the_author. Sounds like they_were chasing
after_every_cool thing to_make_life easy.

Error_handling is a pain yea, I've seen_amateur folk_try catch this and that,
I think_that lends itself to_being_terrible.

One of the things I appreciate_the most about JS is JSON._Crafting tens of
classes in Java_irritates_me._I find Python sometimes tricky_also when dealing
with structs VA lists.

I've_always stuck to_the basics when I was learning how_to_JavaScript with
Node. I used only callbacks_for_2 years until I understood what_my_code_was
doing. Granted, I'd have spaghetti_at the end of complex async_queries, but I
understood what was going on. I moved_to caolan::async and_have been using
async whenever necessary._I_barely_use promises as I got confused by the early
adoption