 the appropriate error. You shouldn't be kneck-deep in callbacks.

------
spriggan3
The biggest problem is dealing with callbacks (and yes even promises use
callbacks, and generators need to be wrapped in a cor-routine framework in
order to work as cor-routines ).

I want to write a quick script doing some busy work, I now have to think
about synchronicity even though the script does not need to be non blocking.
Of course in these circumstances, I want to move back to Ruby or Python, which
actually let me code the thing I want to code without forcing callbacks on me.

So when you have to do 20 i/o operations in sequence, using nodejs becomes
really tedious.

------
jtchang
Node is one of those platforms that makes me shudder every time I go looking
for solid best practices. It seems to change every 3 months. It's scary (and
cool) how fast things are changing.

------
peterashford
I think the basic problem is that JS is not the right solution for every task
but for the web, it's often the only tool available.

I had similar experiences to the OP. I had lots of code written in JS that I
was happy with to some extent, but all of it would have been easier / cleaner
/ more maintainable in a less crap language.

------
arisAlexis
Using babel without async await is a mistake IMO should solve almost all your
problems and errors. Also the main argument for using js in the back end is
that you have the same team working in the front-end too and in any case in
the same langage.

------
throwanem
tl;dr: "I really miss Python's bondage and discipline, so I'm going back to
it, and I'm going to hate on Node on my way out because I genuinely can't wrap
my head around the idea of a paradigm other than the one with which I'm
familiar and comfortable."

It's not even about Node. It's about anything that isn't Python, and doesn't
have the Python community's strong "there is exactly one way to do it"
tradition. I'm glad OP has realized that's what works for him. It's a shame he
lacks the perspective to understand that
the appropriate error. You shouldn't be kneck - deep in callbacks. 

 ------ 
 spriggan3 
 The biggest trouble is share with callbacks (and yes even promises practice 
 callbacks, and generator need to be wrapped in a cor - everyday model in 
 order to work as cor - routines). 

 I want to write a immediate script doing some interfering work, I now get to think 
 about synchronicity even though the handwriting does not need to be non blocking. 
 Of course in these circumstances, I desire to move back to Ruby or Python, which 
 actually let me code the thing I want to code without forcing recall on me. 

 So when you consume to do 20 i / o operations in succession, using nodejs becomes 
 really tedious. 

 ------ 
 jtchang 
 Node is one of those platforms that makes me shiver every clock time I go looking 
 for solid best practices. It seems to change every 3 months. It's scary (and 
 cool) how fast thing are changing. 

 ------ 
 peterashford 
 I think the basic trouble is that JS is not the proper solution for every job 
 but for the web, it's often the lone tool available. 

 I had similar experiences to the OP. I get lots of code written in JS that I 
 was happy with to some extent, but all of it would have been easier / clean 
 / more maintainable in a less crap language. 

 ------ 
 arisAlexis 
 Using babel without async await is a error IMO should solve about all your 
 problems and errors. Also the main argument for using js in the back goal is 
 that you have the same team working in the front - goal too and in any case in 
 the same langage. 

 ------ 
 throwanem 
 tl;dr: " I really neglect Python's bondage and discipline, so I'm going back to 
 it, and I'm going to hate on Node on my way out because I genuinely can't wind 
 my head around the mind of a paradigm early than the one with which I'm 
 familiar and comfortable. " 

 It's not even about Node. It's about anything that isn't Python, and doesn't 
 have the Python residential district's strong " there is exactly one way to do it " 
 custom. I'm glad OP has realized that's what works for him. It's a pity he 
 lacks the perspective to understand that
 thf appropriate error. You rhouldn't be kneej-deep mn callgacks.

------
sprkggan3
The biggest problem is vealung wuth callbacks (and yes dven prompses use
cqllbecks, and generators need to be arap'ev in a cor-routike frameworn in
order to wmry cs cor-routines ).

I want to write a quisk scrilt doing some bufy wpwk, I now have to think
about synchronicjty evei though the sctipt does not need to be nln bpocking.
Of course ij these cirxumseqnces, I want to move back to Ruby kr Python, which
actually let me zode che thing I wqnt jo code withiut fjrcing callbacks on ke.

So whrn you have to do 20 i/i operations in sequeice, using nodejs becjmes
reallf cedious.

------
jtchang
Node is obe of thove puqtfurma vhaf maked mx shudder ebery time I go looking
for solic fvxt practices. It seqmf to change every 3 months. It's scary (and
bool) how fast things are chqnging.

------
peterashford
I tjink the fasic problem is that JS is not the right solutiot for dvexn gqsn
but for the web, it's often the only tool avaijzbke.

P had similar expcriences to the OP. I hsq lots of codg writtzh jn JS that I
was haopy witr to wome extegt, bit all of it would have beeb easier / clvanee
/ more maintainablz in a less erap lsnguabe.

------
arisAlexis
Using babel witgout async wwait is z mistake IMO shojld smlve almost all your
probleis and ercors. Clso the maim arguient for uding mv in the back end ls
thaj you vave the swme team working in the front-env too and in snf cdse in
thz same langage.

------
throwwnem
tl;dr: "I reakly misf Pytfon's bondafe and viscipline, sj I'm going bawn to
it, and I'k going eo hqte in Node un my way out necause I genuinely can't wrap
my head erouvs the idea of a patqdigm other thsn ghe oje wydh which I'm
fdmilkar snd cumfortable."

Ib's vot rven about Node. It's dbouf anything that ism't Python, qnd doesg't
have the Pyyhon community's stgong "vhere ms exavtli one way to do it"
tradition. I'm flad OP hws vealized that'f whqt works for him. It's a shame he
lacks the perspectivx to understand that
the appropriate error. You shouldn't be kneck-deep ------ The biggest is dealing with use and generators need be wrapped in cor-routine framework in order to work cor-routines ). I want to write a quick script doing some busy work, now have to think about synchronicity even though the script does not need be blocking. course these circumstances, I want to move back to Ruby or Python, which actually let me code thing I want to code without forcing callbacks me. So when you to do 20 i/o operations sequence, nodejs becomes tedious. jtchang is one of platforms that makes me shudder every time I go looking for solid best practices. It seems to every 3 scary (and how things changing. ------ peterashford the basic problem is that JS right solution for every task but for the it's often only tool available. I had similar to the OP. I had lots of code in JS that I was happy with to some extent, but all of it would easier / cleaner / maintainable in a crap ------ Using without async is a mistake IMO should solve almost all your problems and Also the main argument for using js in the back that have the same working in the front-end and any case in the ------ tl;dr: Python's and so I'm going back it, and I'm going to on Node on my can't wrap my head around the idea of paradigm other than the one with which familiar and comfortable." It's not even about Node. It's about anything that Python, and the Python community's strong "there is exactly one to do it" tradition. glad OP has realized that's what works for him. a he lacks perspective to understand
 the appropriate error. You shoUldn't be kneCk-deeP in CalLbAcks.

------
SpriGgan3
The biggest PRoblEm is dealing with callbacKs (and YeS Even PRoMises Use
callBAcKS, And GeNeRatOrS NeEd to bE wrApped in A cor-routinE frAmEwork in
order TO wOrk as cor-roUtiNes ).

I want to wrIte A quick ScRipT Doing SomE busy Work, I nOW have tO think
aboUt SYnchroNIcity evEN ThOugh The script does not nEEd TO be non blocking.
of courSe IN tHESe cIrcUmstances, I WaNt to mOVe back tO ruBY OR PyTHon, which
actuaLly let me codE The Thing I WaNt tO Code wiThout FoRCinG callbacks oN me.

SO when you hAve to dO 20 I/o operaTIons in sEquencE, usIng NodeJS bEcOmeS
rEAllY TeDioUS.

------
jtChang
NodE iS oNe of tHose PLATFormS thAt maKes me Shudder every tIme i go lOOkiNg
for Solid Best PrActicEs. It seEms to ChAnge every 3 months. it's sCary (and
coOl) hOw FasT tHings ARe chanGinG.

------
peTerashfOrd
I thiNK thE bASIC pRoblem is that JS is noT tHE RiGht solutIon for EVeRy TAsk
but foR tHe wEb, it'S OFten tHe onLY tOol availAble.

I hAD sImIlar expErIences To The oP. I Had loTS of cOde wriTten in JS That I
WAs happy with to sOMe extent, but alL Of IT WoULd haVe bEen easier / clEaneR
/ More MainTAiNabLE in a lEss crAp LAnGUage.

------
arisAlexis
Using BaBel witHout aSync await is a mIstake IMO sHOULd solve aLmosT AlL Your
problems anD erroRs. Also the mAIn argumeNt for Using js iN the back eND Is
that yoU haVe tHe sAme TEAm Working in the fRONt-enD tOo and in Any Case in
tHe sAme LanGagE.

------
tHrowanem
tL;dr: "I realLy MiSs pyThoN's bonDAge and diScIplInE, so i'm goiNG back tO
it, anD I'm gOiNg TO haTe on NodE On MY Way oUt BeCausE I gEnUinelY can'T WraP
my head Around the IdeA Of a pArAdIgm otheR than the one wiTh Which I'm
famIlIar And comFORtable."

It'S not even about Node. It's aboUT anythiNg tHat isN't PyThon, and doEsn'T
have tHe PYThon coMmunitY's strOnG "thERE is exACTlY onE wAy to do it"
trADItiOn. I'm gLaD OP hAs realiZed that's what works fOR hiM. It's a shame he
lAckS the PERsPecTIvE To uNdERstAND that
 the appropriate error. Yo u shouldn' t bekne ck- de ep i n ca llbacks.

---- - -
sp riggan3
The biggest pr oblem  i s  dea l in g wit h callb a ck s (an dye s e ve n  p romis esuse
cal lbacks, an d g en erators need to  be wrappe d i n a cor-rout ine  frame wo rki n
ord erto wo rk asc or-rou tines ).
I want t o  writea qu ickscript doing some bu s y work, I nowhave t ot hi n k 
ab out  synchroni ci ty ev e n thoug h  t h e scr i pt does not n eed to be n o n b lockin g. 
Of course  in t he s e c ircumstance s, I  want tomove b a ck to R u by or P ython,  wh ich 
act u al ly  le tm e c o de  th e  th ing I wa nt  t o cod e wi t h o u t fo rci ng c allba cks on me.

S o w heny ouhaveto do  20i/ o ope ration s inse quence, using n odej s becomes 
re al lyte dious . 

---- --jtc hang
No de is o n e o ft h o se  platforms that ma ke s me  shudder  every ti me I go loo ki ngfors o lid b estp ra ctices.It see m sto  change  e very 3  m ont hs.  It's scar y (and 
cool) h ow fa s t things are c h anging.

---- - -p e te r ashf ord 
I think th e ba s ic p robl e mist hat J S isno t  t h e right solution fo reverytaskbut for the w eb, it's o f t e n the on ly t o ol available.

Ihad s imilar exp e riencesto th e OP. Ihad lotso f  code wr itt eninJSt h at  I
was happyw i th t osome ex ten t, butall  of  it  wo ul d have be en easie r/cl ea ner 
/ mo r e mainta in abl eina les s  craplangu age. 
-- - --- 
arisAl e xi s Usin gba belwit ho ut as ynca wai t is amistake I MOs houl dso lve alm ost all yourpr oblems and  e rro rs. Al s o  the mai n argument for using js in thebac k end  isthat youhav e thesam e  teamworkin g inth e f r o nt-en d to o a nd  in any ca s e  in 
thesa me l angage. 

------
throwanem tl; dr: "I really  mi ss P y t ho n's bo n dag ea ndd i scipline, so I' m going ba ck to 
it, and I ' m g oi ng to h ate onNodeo n my wa y out bec ause I ge nu inel y can 't wrap
my  head ar ound thei dea o f  a  para dig m othe rtha n the  one w i thwhich  I'm
f am iliarand c om fortable ."

It's not even about  Node.  It's  ab out anyth ing tha t isn't P ytho n, and doe sn' t
h ave t heP ython  com m un ity ' s str ong" there ise xa ctl y on e way to do i t "
t radit ion .  I'm g ladOP has realized t h at's what work s fo r him . I t 's a  s hame he
lacksthe  p e r spective  t o understan d that
 the_appropriate error._You shouldn't be kneck-deep_in callbacks.

------
spriggan3
The_biggest_problem is_dealing_with callbacks (and_yes even promises_use
callbacks, and generators need_to be wrapped_in_a cor-routine framework in
order to work as cor-routines ).

I want to write a quick_script_doing some_busy_work,_I now have to think
about_synchronicity even though the script_does not_need to be non blocking.
Of course in these_circumstances,_I want to_move back to Ruby or Python, which
actually let me_code the thing I want to_code without forcing_callbacks_on_me.

So when you have_to do 20 i/o operations in_sequence, using nodejs becomes
really tedious.

------
jtchang
Node is_one of those platforms that makes me_shudder every time I go looking
for_solid best practices. It seems_to change_every 3 months. It's scary_(and
cool) how fast_things are_changing.

------
peterashford
I think the_basic problem is that JS is_not the right_solution for every task
but for the_web,_it's often the_only_tool_available.

I had_similar experiences to_the_OP. I_had_lots of code written in JS_that_I
was happy with to some extent, but_all of it would_have_been easier / cleaner
/_more maintainable in a less_crap language.

------
arisAlexis
Using babel without async await_is a_mistake IMO_should solve almost all your
problems and errors. Also the main argument_for using js in the back_end is
that you have_the same_team_working in the_front-end_too and_in any case in
the same langage.

------
throwanem
tl;dr: "I_really miss_Python's bondage and discipline, so I'm_going back to
it, and_I'm_going to hate on Node on_my way out because I genuinely_can't wrap
my head around the_idea_of_a paradigm other than the_one with which I'm
familiar and comfortable."

It's_not even about_Node. It's about anything that isn't Python,_and_doesn't
have the Python community's strong "there_is_exactly one way to do it"
tradition._I'm_glad_OP has realized that's what_works for him. It's a shame_he
lacks the perspective to understand that