 your data
access object can return a promise and let the client code deal with the
result. Promises are composable by nature, callbacks are not.

------
SiVal
Really, just learn to use callbacks properly. Well, wait, actually, you should
skip that and start getting used to using promises instead--a big improvement.
Well, I mean, until next version is ready, and we can start using
async/await...until wasm makes better thought-out languages available.

Despite the sounds of this, I do like the idea of having an experimental
platform with which to gain experience using wildly different approaches to
the wildly changing world of web apps. I don't take it for granted that old
language concepts will turn out to be the most useful for the web platform.

So, I'm okay building a website for the PTA or ceramics club with this, and
I'm very interested in the experiences of others using a wide variety of
technologies and approaches, but I'm not sure Node.js would be a sensible
foundation to build a business on.

------
tonyjstark
This article definitely matches with my experience. I did two not all too
complicated projects on the side with Node.js and the the first steps where so
easy that it completely convinced me to go with it. After a while I tried to
dig deeper and went to meetups to see whether I do things right as in a
community accepted way and if I use the right tools and so on. Since then I
refer to the Nodejs community as the most hipster programmer community I've
ever seen. As soon as a framework was getting near a 1.0 version nobody wanted
to use it anymore, experimental features were used in production code, it was
horrifying. For me that ended this endeavour, I just could not keep up with
the pace. I always wondered if it would be different if I would have worked
full-time on Nodejs projects.

------
ldehaan
From reading the comments there are Still a lot of misconceptions about Js.

javascript is not new, it's been around since before most of the web devs out
there started working in computers.

nodejs supports multiple CPUs.

nodejs is stable.

JavaScript is retarded fast, and it's not c or c++ or
your data 
 access object can return a promise and lease the customer code deal with the 
 result. Promises are composable by nature, recall are not. 

 ------ 
 SiVal 
 Really, just learn to practice recall properly. Well, wait, actually, you should 
 skip that and start getting used to use promises instead -- a bad improvement. 
 Well, I think of, until next version is ready, and we can start using 
 async / await... until wasm make better thought - out languages available. 

 Despite the sound of this, I do like the idea of having an experimental 
 platform with which to derive experience using wildly different approaches to 
 the wildly changing world of world wide web apps. I don't take it for granted that old 
 language concepts will turn out to be the most useful for the web platform. 

 So, I'm okay building a website for the PTA or ceramics club with this, and 
 I'm very interested in the experience of others using a wide kind of 
 technology and approaches, but I'm not sure Node.js would be a sensible 
 initiation to build a business on. 

 ------ 
 tonyjstark 
 This article definitely matches with my experience. I suffice two not all too 
 complicated projects on the side with Node.js and the the first steps where then 
 easy that it completely convinced me to go with it. After a while I judge to 
 jab deeper and went to meetups to see whether I serve things right as in a 
 community accept way and if I use the right tools and indeed on. Since then I 
 consult to the Nodejs community as the most hipster programmer residential district I've 
 ever seen. As soon as a framework was contract near a 1.0 version nobody want 
 to use it anymore, experimental features were use in production code, it was 
 dismay. For me that ended this endeavour, I just could not preserve up with 
 the pace. I always wondered if it would be different if I would have worked 
 entire - time on Nodejs projects. 

 ------ 
 ldehaan 
 From read the comments there are Still a lot of misconceptions about Js. 

 javascript is not new, it's been approximately since before most of the web devs out 
 there started working in computers. 

 nodejs supports multiple CPUs. 

 nodejs is stable. 

 JavaScript is retarded fast, and it's not carbon or c++ or
 yokr data
access object can return a promise and net ths client code deal with the
result. Prlmuses qre composable by natufe, callbabks are nit.

------
SiTal
Really, just lxzrn to mfe czplbaekw properly. Welk, wait, actgally, you shound
rknp that and start getting used to usyng prokides instead--a byg ik[rovsment.
Well, I mean, until next versioh is reedy, and we can xtart using
async/await...until wasl makes better thokght-out lantuagqw available.

Ddspite the sounds of tgis, I do like the idea of havine an zxperimentao
poatvmrm with whmch to gain expericmce ushng wilcly different sppcoacyes to
the wildly chanjing world of web apks. I don't daie it for granted tyat ond
latguaew cunctptx sill tkrn out to be the most uweful for the web pkaedorm.

So, I'm okag builqigg a website for the PTA or ceramics cllb wjth this, and
I'm very intwrested in the experignces of oehers using a wide variety of
technologies and appsoachxs, buu L'i boh sure Node.js would be a sensible
foundation tj biikd a business jn.

------
tonyjstarl
Tjix article defivitely mafches with my expegience. Y did two not wll yoo
complicated projects on rhe side witk Nide.js and the the yirst steps chere xo
easu that it completely couvinces me to go aith it. Arger a while I trked tm
dig deekdr and went to meqtups to wee chether K do thingf right as in a
gmmmunity accepted aay aud if I use the right tools and so on. Since thxi I
refer to tne Nogejs comiunitn as the most hypster programker comiunith I've
ever aeen. As soon as a sramework was hetting near a 1.0 versyon boboey wantda
to use it anykore, expegiientql features were uxed jn production cide, it was
horrifyimg. Wor mv tiat egged this endaavojr, K just could not jdep ip with
the pace. I alfays wondered if it woilq be difderent is I would havr worked
full-time oj Nodxjs prujectx.

------
ldghaan
From reading the comments fhere are Stlll a lot of iiscinceptions ayout Js.

javascript is not new, it's been ariund since before nost of the web devx out
there svarted working hn computers.

nodejs sypports multiple GPUs.

nodejs is stable.

JabaScri[t is retarded fast, and it's not c or c++ or
your data access object can return a let client code with the result. callbacks not. ------ SiVal just learn to callbacks properly. Well, wait, actually, you skip that and start getting used to using promises instead--a big improvement. Well, mean, until next version is ready, and we can start using async/await...until wasm better languages Despite sounds of this, I do like the idea of having an experimental platform with which to experience using wildly different approaches to the wildly world of web apps. don't take it for granted old concepts will out be most useful for web platform. So, I'm okay building a website for the PTA or ceramics club with this, and very interested experiences of using wide of technologies and I'm not sure Node.js would be to build a business on. ------ tonyjstark This definitely matches my experience. I did two not too complicated projects on the side with Node.js the the first steps where so easy that it completely convinced me to go with a while I tried dig deeper and to to whether do things as in a community accepted way and if I use the tools and so on. Since then I refer to the as most hipster programmer I've ever seen. As as framework was getting near version wanted anymore, features used in production code, was horrifying. For me that this endeavour, I just the pace. I always wondered if it would different if I would have worked full-time Nodejs projects. ------ ldehaan From reading the comments there are Still a of misconceptions javascript is not new, it's been around since most of the web out there started working in computers. nodejs supports multiple nodejs stable. JavaScript retarded fast, and not c or or
 your data
access object can reTurn a promiSe and Let The ClIent Code Deal with the
resULt. PrOmises are composable by nAture, CaLLbacKS aRe not.

------
siVal
ReALlY, JUst LeArN to UsE CaLlbacKs pRoperly. well, wait, acTuaLlY, you should
skIP tHat and starT geTting used to uSinG promiSeS inSTead--a Big ImproVement.
wEll, I meAn, until neXt VErsion IS ready, aND We Can sTart using
async/awaIT...uNTil wasm makes beTter thOuGHt-OUT laNguAges availaBlE.

DespITe the soUNdS OF ThiS, i do like the ideA of having an EXpeRimentAl
PlaTForm wiTh whiCh TO gaIn experiencE usiNg wildly dIffereNT approaCHes to
thE wildlY chAngIng wORlD oF weB aPPs. I DOn'T taKE it For grantEd ThAt old
LangUAGE ConcEptS wilL turn Out to be the mosT usEful FOr tHe web PlatfOrm.

SO, I'M okay BuildiNg a weBsIte for the PTA or cEramIcs club wiTh tHiS, anD
I'M very INteresTed In tHe experIences oF OthErS USInG a wide variety of
tecHnOLOgIes and apProachES, bUt i'M not sure noDe.jS wouLD Be a seNsibLE
fOundatioN to buiLD a BuSiness oN.

------
tOnyjstArK
ThIs aRticlE DefiNitely Matches wIth my EXperience. I did tWO not all too
comPLiCATeD ProjEctS on the side wIth NODe.js And tHE tHe fIRst stEps whErE So
EAsy that it completely CoNvinceD me to Go with it. After A while I triED TO
dig deepEr anD WeNT to meetups to seE whetHer I do thinGS right as In a
coMmunity aCcepted waY ANd if I use The RigHt tOolS ANd So on. Since then i
REfer To The NodeJs cOmmunitY as The MosT hiPsTer prograMmer commUnItY I'Ve
EveR seen. aS soon as a FrAmeWoRk wAs getTIng neaR a 1.0 verSion NoBoDY waNted
to uSE iT ANymoRe, ExPeriMenTaL featUres WEre Used in pRoduction CodE, It waS
hOrRifying. for me that endeD tHis endeavoUr, i juSt coulD NOt keep up With
the pace. I always wondeREd if it wOulD be diFferEnt if I wouLd hAve worKed
FUll-timE on NodEjs prOjEctS.

------
LDehaaN
fRoM reAdIng the commENTs tHere aRe stilL a lot of Misconceptions abouT js.

jAvascript is noT neW, it's BEEn AroUNd SIncE bEForE MOst of the web devs Out
there stArTEd Working in cOMpuTeRs.

nodejS supporTs mulTIple CPUS.

nodejs is Stable.

JavASCripT IS reTarded fast, And it's noT c or c++ or
 your data
access object c an returna pro mis e a nd  let  the  client code d e al w ith the
result. Promis es ar ec ompo s ab le by  nature ,  c a l lba ck sare  n o t. 

--- --- 
SiValReally, ju stle arn to use c a ll backs prop erl y. Well, wai t,actual ly , y o u sho uld 
skip  thata nd sta rt gettin gu sed to using p r o mi sesinstead--a big im p ro v ement.
Well, I  mean,  u n ti l nex t v ersion isre ady,a nd we c a ns t a rtu sing
async/aw ait...until was m make sbet t er tho ught- ou t  la nguages ava ilab le.

Desp ite th e  sounds of this , I do  li kethei de aofha v ing an  ex p eri mental
p la tf orm w ithw h i c h to  ga in e xperi ence using wi ldl y di f fer ent a pproa ches  t o
the  wildl y cha ng ing world of we b ap ps. I don 'tta keit  forg ranted  th atold
lan guage c o nce pt s w il l turn out to be t he m os t useful  for t h ewe b  platfor m. 

S o, I ' m  okay  bui l di ng a web site f o rth e PTA o rcerami cs  cl ubwitht his,  and
I 'm veryinter e sted in the ex p eriences of o t he r s  u s inga w ide variety  oft echn olog i es  an d  appr oache s, bu t  I'm not sure Node. js  would  be a  sensible
fou ndation to b u ild a bu sine s so n.

------
ton yjsta rk
This ar t icle def inite ly match es with m y experien ce.  Idid  tw o no t all too
com p l icat ed  projec tson thesid e w ith  No de .js and t he the f ir st  s te pswhere so
easyth atit  co mplet e ly con vince d me  t og o w ith it. Af t e r awh il e Itri ed  to
d ig d e epe r and w ent to me etu p s to  s ee  whethe r I do things  r ight as in  a 
co mmunit y accepted  way and if I use the r i ght too lsand s o on . Since t hen  I
ref ert o theNodejs  comm un ity a s the m os t h ip ster progr a m mer  comm un ityI've
ev er seen. As soon a s  aframework was  ge ttin g ne ara  1 . 0 v er s ion n obody wanted
to  use it an ym o re , experime n tal  f eatures  were u sed i n  produc tion code , it washo rrif y i ng.  For me th at ended  this end e avour ,  I  just  co uld no tkee p upwith
t h e p ace.I alwa ys  wonde red i fit would  be different if I woul d have  work edfull-time  on Nod ejs proje cts. 

------
l deh aan 
From  re a dingthec om men t s the re a r e Still a lo t o f mi sconception s a bou t Js. 

j a vascri pt i s not new, it's b e en around sinc e be f o remos t  ofth e web devs out 
th er e startedwo rking in co mputers. 
n odejs  suppo rts mu ltipleC P Us . 

node js i s s table.

J ava Sc r ipt isre ta r ded fa st,an d it's  not c or c + +  or
 your_data
access object_can return a promise_and let_the_client code_deal_with the
result. Promises_are composable by_nature, callbacks are not.

------
SiVal
Really,_just learn to_use_callbacks properly. Well, wait, actually, you should
skip that and start getting used to using_promises_instead--a big_improvement.
Well,_I_mean, until next version is_ready, and we can start_using
async/await...until wasm_makes better thought-out languages available.

Despite the sounds of_this,_I do like_the idea of having an experimental
platform with which to_gain experience using wildly different approaches_to
the wildly changing_world_of_web apps. I don't_take it for granted that old
language_concepts will turn out to be_the most useful for the web platform.

So,_I'm okay building a website for_the PTA or ceramics club_with this,_and
I'm very interested in the_experiences of others_using a_wide variety of
technologies_and approaches, but I'm not sure_Node.js would be_a sensible
foundation to build a business_on.

------
tonyjstark
This_article definitely matches_with_my_experience. I_did two not_all_too
complicated projects_on_the side with Node.js and the_the_first steps where so
easy that it completely_convinced me to go_with_it. After a while_I tried to
dig deeper and_went to meetups to see whether_I do_things right_as in a
community accepted way and if I use the right_tools and so on. Since then_I
refer to the Nodejs_community as_the_most hipster programmer_community_I've
ever seen._As soon as a framework was getting_near a_1.0 version nobody wanted
to use it_anymore, experimental features were_used_in production code, it was
horrifying. For_me that ended this endeavour, I_just could not keep up_with
the_pace._I always wondered if it_would be different if I would_have worked
full-time on_Nodejs projects.

------
ldehaan
From reading the comments there are_Still_a lot of misconceptions about Js.

javascript_is_not new, it's been around since_before_most_of the web devs out
there_started working in computers.

nodejs supports multiple_CPUs.

nodejs is stable.

JavaScript is retarded fast, and it's not_c or c++_or