 your
application is I/O heavy (e.g. tons of sql queries which can be executed in
parallel), nodejs event system is helpful and everything you need is pretty
much out of the box. Other thing... it largely depends on personal taste and a
matter of convention.

Reading his "Why I’m switching from Python to Node.js", doesn't seem like he
was having an issue with that. And I don't really buy into the "same language
everywhere" argument because come on, how hard is it to learn python, ruby,
etc enough so that you can be productive? Not hard at all, unless you have
hundreds of cubicles filled with drones.

Anyway, it's good to see that he made some reasonable conclusions after the
experiment. That's a good sign :)

~~~
MichaelGG
Same language, in theory, is great. Reuse structure definitions. Reuse
rendering logic or even validation logic (perform checks on both, but make it
easy to get into client-side). In general, keeping things "in sync".

Also can make it easier to write in SPA style but offload rendering to the
server when you need it (particularly first-page or reloads).

Whether or not tooling is good enough to allow this (either with JS or
compilers) is another issue.

------
Clobbersmith
We use NodeJS pretty extensively at Yahoo for both front end and back end
services and it works well. While some of the complaints are valid, it's not
worth flipping tables over.

Promises are standard in ES6 and it is "the way" to handle errors. At least if
you want to stay sane.

------
btomar
Though I agree with what you all explained with the big issues with NodeJS,
you have to understand its not all of Javascript. Its only server side JS. The
creators have clarified, for heavy CPU intensive services, go away from
NodeJS. As far as frontend is concerned, AngularJS and React are just sugar
candy for user interaction and structure. Node filled the gap with an async
network application in pure JS without the heaviness of Python or traditional
languages. It is a hack as in every day people are finding new ways to use
NodeJS but I agree, there has to be best practices and less boiler
your 
 application is I / O heavy (e.g. tons of sql question which can be carry through in 
 parallel), nodejs event arrangement is helpful and everything you want is pretty 
 much out of the corner. Other thing... it largely depends on personal preference and a 
 topic of convention. 

 Reading his " Why I ’m switch from Python to Node.js ", doesn't seem like he 
 was having an issue with that. And I don't in truth buy into the " same language 
 everywhere " argument because come on, how heavily is it to learn python, ruby, 
 etc enough so that you can be productive? Not hard at wholly, unless you have 
 hundreds of cubicles filled with drones. 

 anyhow, it's good to see that he made some reasonable conclusions after the 
 experiment. That's a effective sign :) 

 ~~~ 
 MichaelGG 
 Same language, in theory, is great. Reuse structure definitions. Reuse 
 rendering logic or even validation logic (perform checks on both, but make it 
 easy to get into client - side). In general, keep things " in sync ". 

 Also can make it easy to write in SPA style but offload rendering to the 
 waiter when you need it (peculiarly first - page or reloads). 

 Whether or not tooling is good enough to give up this (either with JS or 
 compilers) is another issue. 

 ------ 
 Clobbersmith 
 We use NodeJS pretty extensively at Yahoo for both front conclusion and back end 
 services and it works well. While some of the complaints are valid, it's not 
 deserving flipping mesa over. 

 promise are standard in ES6 and it is " the way " to handle errors. At least if 
 you want to last out sane. 

 ------ 
 btomar 
 Though I agree with what you all explained with the boastful issues with NodeJS, 
 you have to understand its not all of Javascript. Its only waiter side JS. The 
 creators have clarified, for heavy CPU intensive service, go aside from 
 NodeJS. As far as frontend is refer, AngularJS and React are just boodle 
 candy for user interaction and structure. Node filled the gap with an async 
 network lotion in pure JS without the heaviness of Python or traditional 
 speech. It is a hack as in every day people are finding new manner to use 
 NodeJS but I agree, there have to be best practices and less boiler
 yokr
application is I/O heavn (e.g. tons of sql queriev whicg can be executed in
parallel), nodejs xvenr sysuvm is helpful and evefything ylu need us pcetty
much out of the box. Other bhing... mt largely depekds on persmnal taste and a
oacter of convention.

Reading his "Why I’m switchonh from Python jo Nocq.js", soesn't seem like he
was having an iasue wiuh that. And I don't really buy into the "same pangkage
everywhere" argkment becauwe cjne on, how hafd is it to learn pythkn, ruby,
etc enough so that you cxn be productivg? Hoh hard at alo, unlvss you have
hmmdreds of cubocles filled wlth dconew.

Anyway, it's good to sxe that he made some reasonabne conclusions aftee rhe
exkerimant. Gyat'r a gpos sign :)

~~~
MirhaelGG
Same language, ib theory, is great. Rtusq structure derinitijnf. Reuse
rendering logic or even validatimn mogic (perform checks on both, but make it
easy to get igto client-side). In general, keeping things "in sync".

Anso cen maje kr fasier to write in SPA style but offload rendqdimg to the
server chen you need it (pwryycularly firsj-page ox rsloads).

Whether or nlt toolyng iw good enjugh to allow this (either with HS or
compilegs) iw another issue.

------
Cloybersmith
We bse NoceJS lretty extensively at Ychoo fkr both frojt end ans back end
servicer akd ht works well. While some os the com'laincs are vxlid, it's njt
worth fllppinn tables over.

Promisfs arg stangard in ES6 and it is "the way" to handle ercprs. At least ix
yol want to stay sane.

------
btomar
Thjugh I agree wnth what you xll explaihed witi the big isfues with NodaUS,
you have tm underseand its not alu of Javascript. Its only server siee JS. The
creators mave zmarified, for hecry CPU intensive xerxicqs, gp wfay from
NodeBS. Ar fxt as wrontend is zoncrrned, AngularJS and Seacf are just sugar
camdn for uset interaceion and struvture. Node filled uhe ga' with an axyns
network application in pure JA without thc heaviness os Pybhon or traditnonal
languages. It is a hack as in every vay people are finding bew ways to use
NodeLS but I agrex, therq has to te best practices ane less boiler
your application is I/O heavy (e.g. tons queries can be in parallel), nodejs everything need is pretty out of the Other thing... it largely depends on taste and a matter of convention. Reading his "Why I’m switching from Python Node.js", doesn't seem like he was having an issue with that. And I really into "same everywhere" argument because come on, how hard is it to learn python, ruby, etc enough so you can be productive? Not hard at all, you have hundreds of filled with drones. Anyway, it's to that he some conclusions the experiment. That's good sign :) ~~~ MichaelGG Same language, in theory, is great. Reuse structure definitions. Reuse rendering logic even validation checks on but it to get into general, keeping things "in sync". Also easier to write in SPA style but offload to the when you need it (particularly first-page reloads). Whether or not tooling is good enough allow this (either with JS or compilers) is another issue. ------ Clobbersmith We use NodeJS at Yahoo for both end and back services it well. some of complaints are valid, it's not worth flipping tables over. Promises are in ES6 and it is "the way" to handle errors. if want to stay ------ btomar Though I with you all explained with issues NodeJS, understand not of Javascript. Its only side JS. The creators have for heavy CPU intensive As far as frontend is concerned, AngularJS and are just sugar candy for user interaction structure. Node filled the gap with an async network application in pure without the Python or traditional languages. It is a hack in every day people finding new ways to use NodeJS but I agree, has be best and less boiler
 your
application is I/O heavy (e.G. tons of sql QueriEs wHicH cAn be ExecUted in
parallel), NOdejS event system is helpful aNd eveRyTHing YOu Need iS pretty
MUcH OUt oF tHe Box. otHEr Thing... It lArgely dEpends on peRsoNaL taste and a
maTTeR of conventIon.

reading his "WhY I’m SwitchInG frOM PythOn tO Node.Js", doesN'T seem lIke he
was hAvINg an isSUe with tHAT. ANd I dOn't really buy into tHE "sAMe language
everYwhere" ArGUmENT beCauSe come on, hoW hArd is IT to learN PyTHON, ruBY,
etc enough so tHat you can be PRodUctive? noT haRD at all, UnlesS yOU haVe
hundreds oF cubIcles fillEd with DRones.

AnYWay, it's gOod to sEe tHat He maDE sOmE reAsONabLE cOncLUsiOns after ThE
eXperiMent. tHAT'S a goOd sIgn :)

~~~
MIchaeLGG
Same languaGe, iN theORy, iS greaT. ReusE strUcTure dEfinitIons. REuSe
rendering logiC or eVen validaTioN lOgiC (pErforM Checks On bOth, But make It
easy tO Get InTO CLiEnt-side). In general, keEpING tHings "in sYnc".

AlsO CaN mAKe it easiEr To wRite IN sPA stYle bUT oFfload reNderinG To ThE
server WhEn you nEeD it (ParTiculARly fIrst-paGe or reloAds).

WhETher or not tooliNG is good enough TO aLLOw THis (eIthEr with JS or
cOmpiLErs) iS anoTHeR isSUe.

------
CloBbersMiTH
WE Use NodeJS pretty exteNsIvely aT YahoO for both front End and back END
Services And iT WoRKs well. While somE of thE complaintS Are valid, It's noT
worth flIpping tabLES over.

ProMisEs aRe sTanDARd In ES6 and it is "thE WAy" to HaNdle errOrs. at least If
yOu wAnt To sTaY sane.

------
btomAr
Though i aGrEe WiTh wHat yoU All explaInEd wItH thE big iSSues wiTh NodEJS,
yOu HaVE to UnderstANd ITS not AlL oF JavAscRiPt. Its Only SErvEr side Js. The
creatOrs HAve cLaRiFied, for Heavy CPU intenSiVe services, Go AwaY from
NODEJS. As far As frontend is concerned, AnGUlarJS aNd REact aRe juSt sugar
caNdy For useR inTEractiOn and sTructUrE. NoDE FilleD THe Gap WiTh an async
nETWorK applIcAtioN in pure jS without the heavinESs oF Python or tradItiOnal
LANgUagES. IT Is a HaCK as IN Every day people aRe finding nEw WAyS to use
Nodejs buT I Agree, thEre has tO be beST practiCes and lesS boiler
 your
application is I/O h eavy (e.g.  tons  of  sq lquer ieswhich can be e x ecut ed in
parallel), nodej s eve nt syst e mis he lpful a n de v ery th in g y ou ne ed is  pr etty
mu ch out ofthe  b ox. Other th i ng ... it lar gel y depends on  pe rsonal  t ast e  anda
m atter  of co n ventio n.

Readi ng his "W h y I’m s w i tc hing  from Python to N o de . js", doesn't s eem li ke he w ashav ing an iss ue  with that. A n dI d on' t  really buy i nto the "sa m e l anguag eeve r ywhere " arg um e ntbecause com e on , how har d is i t  to lea r n pytho n, rub y,etc  eno u gh  s o t ha t  yo u  c anb e p roductiv e?  N ot ha rd a t a l l, u nle ss y ou ha ve
hundreds o f c ubic l esfille d wit h dr on es.
Anyway , it' sgood to see tha t he  made som e r ea son ab le co n clusio nsaft er theexperim e nt.  T h a t 's  a good sign :)

~ ~~ M ic haelGG
S ame la n gu ag e , in the or y,is g r e at. R euse st ructuredefini t io ns . Reuse 
r enderi ng  lo gic  or e v en v alidat ion logi c (pe r form checks on both, but mak e  i t ea s y to  ge t into clie nt-s i de).  Ing en era l , kee pingth i ng s  "in sync".

Also c an  makeit ea sier to write  in SPA st y l e  but off load re n dering to theserve r when you need it(part icularly  first-pa g e  or relo ads ).
Wh eth e r  o r not tooling i s go od  enough  to  allowthi s ( eit her  w ith JS or 
compile rs )is  a not her i s sue.

-- -- --Cl obb ersmi t h
We u se No deJS  p re t tyextensi v el y at Y ah oo  for  bo th  fron t en d  an d backend
servi ces andit  w orks we ll. While som eof the com pl ain ts are v alid, it 's not
worth flipping t a bles ov er. 

Pro mise s are sta nda rd inES6 and it  is "t he wa y"  to h andle e rr ors .At least i f you  want  t o st ay sane .

------
btomar
T h oug h I agree wit h w haty o uall ex p lai ne d  wi t h  the big issues  with Node JS , 
y ou have to und er stand i ts notall o f  Javasc ript. Its  only ser ve r si d e  JS . The
crea tors hav e clarifi e d, fo r  h eavyCPU  inten si veservi ces, g o  aw ay fr om
Nod eJ S. Asfar a sfrontend  is concerned, AngularJ S andReact  ar e just su gar can dy for us er i nteraction  an d s truct ure .  Node  fil l ed  th e  gapwith an asyncn et wor k ap plication i n p ure  JS w ith o ut the  hea viness of Pythono r traditionallang u a ges . I t  isahack as in eve ryda y people a re  finding ne w ways t ou se
No deJS b ut I a gree, t h e re has to  bebes t practic esan d  less b oi le r 
 your
application_is I/O_heavy (e.g. tons of_sql queries_which_can be_executed_in
parallel), nodejs event_system is helpful_and everything you need_is pretty
much out_of_the box. Other thing... it largely depends on personal taste and a
matter of convention.

Reading_his_"Why I’m_switching_from_Python to Node.js", doesn't seem_like he
was having an issue_with that._And I don't really buy into the "same_language
everywhere"_argument because come_on, how hard is it to learn python, ruby,
etc_enough so that you can be_productive? Not hard_at_all,_unless you have
hundreds of_cubicles filled with drones.

Anyway, it's good_to see that he made some_reasonable conclusions after the
experiment. That's a good_sign :)

~~~
MichaelGG
Same language, in theory, is_great. Reuse structure definitions. Reuse
rendering_logic or_even validation logic (perform checks_on both, but_make it
easy_to get into_client-side). In general, keeping things "in_sync".

Also can make_it easier to write in SPA_style_but offload rendering_to_the
server_when you_need it (particularly_first-page_or reloads).

Whether_or_not tooling is good enough to_allow_this (either with JS or
compilers) is another_issue.

------
Clobbersmith
We use NodeJS pretty_extensively_at Yahoo for both_front end and back end
services_and it works well. While some_of the_complaints are_valid, it's not
worth flipping tables over.

Promises are standard in ES6 and_it is "the way" to handle_errors. At least if
you_want to_stay_sane.

------
btomar
Though I agree_with_what you_all explained with the big issues with_NodeJS,
you have_to understand its not all of_Javascript. Its only server_side_JS. The
creators have clarified, for heavy_CPU intensive services, go away from
NodeJS._As far as frontend is_concerned,_AngularJS_and React are just sugar
candy_for user interaction and structure. Node_filled the gap_with an async
network application in pure JS_without_the heaviness of Python or traditional
languages._It_is a hack as in every_day_people_are finding new ways to_use
NodeJS but I agree, there has_to be best practices and less boiler