 world from the db, service the request, and then destroy the world
you've just created. For structural things like MVC, objects are great, but
you really don't see much of the "object as vehicle for data encapsulation"
that's drilled into every new programmer when they're first taught OOP.

The client, on the other hand, _can_ persist data and objects through
requests, and the only time it needs to be fully refreshed is on a full
reload.

~~~
cwp
Ah. But that isn't an issue of language or object-orientation. There are
server-side frameworks that _don't_ throw away the world, and client-side
frameworks that do. (Notice how your javascript state is thrown away everytime
you load a new page in the browser). That's a design decision that's made
possible by the statelessness of HTTP, but not required by it.

~~~
gbog
Certainly, but throwing away the world is natural on server side code and it
means that your carefully crafted object don't live long and many of them
don't need too be objects, they are micro namespaces for a set of methods. I
never tried node.js for real but one good side off it could be that you are
not pushed towards objects like you are with Python, Ruby, Java, etc.

------
leephillips
The author refers to this seething criticism of node
(<http://teddziuba.com/2011/10/node-js-is-cancer>. html), that I've seen
before, and then just soldiers on without addressing it. I'm not well versed
enough to know whether Dziuba's analysis is not the mark or not. What do the
javascript/node experts here have to say about it? The criticism, after all,
would seem to be so damning that it either needs to be refuted or to stand as
a definitive reason to never seriously consider using node in a real project.

------
octotoad
Just read around two thirds of 'The Node Beginner Book'. I've only briefly
played with node.js before now and I still don't really have an immediate use
for it personally. I could see myself using it to whip up rough scaffolding to
support prototypes of personal projects written in other languages.

I did learn something from its
world from the db, service the request, and then destroy the world 
 you've barely create. For structural things like MVC, objects are capital, but 
 you really don't see much of the " aim as vehicle for data encapsulation " 
 that's drilled into every fresh programmer when they're first taught OOP. 

 The node, on the other hand, _ can _ persevere datum and objects through 
 requests, and the lone time it needs to be amply refreshed is on a full 
 reload. 

 ~~~ 
 cwp 
 Ah. But that isn't an issue of terminology or object - orientation. There are 
 server - slope frameworks that _ don't _ throw away the world, and client - slope 
 frameworks that do. (Notice how your javascript state is thrown away everytime 
 you load a new page in the browser). That's a design decision that's made 
 possible by the statelessness of HTTP, but not required by it. 

 ~~~ 
 gbog 
 Certainly, but throwing away the world is natural on server slope code and it 
 means that your carefully craft aim don't live long and many of them 
 don't need too be objects, they are micro namespaces for a hardening of methods. I 
 never tried node.js for real but one good slope off it could be that you are 
 not pushed towards objects like you are with Python, Ruby, Java, etc. 

 ------ 
 leephillips 
 The author refers to this seething criticism of node 
 (< http://teddziuba.com/2011/10/node-js-is-cancer >. html), that I've seen 
 before, and then precisely soldiers on without addressing it. I'm not well versed 
 enough to acknowledge whether Dziuba's analysis is not the scratch or not. What do the 
 javascript / node experts here have to say about it? The criticism, after wholly, 
 would seem to be so damning that it either needs to be refuted or to stand as 
 a definitive reason to never seriously regard using lymph node in a real project. 

 ------ 
 octotoad 
 Just read around two thirds of' The Node Beginner Book'. I've merely briefly 
 play with node.js before now and I even don't really have an immediate use 
 for it personally. I could see myself use it to whip up grating scaffolding to 
 support prototypes of personal projects write in early languages. 

 I did learn something from its
 wogld from the db, service uhe request, and tkwn desvroy ths world
yuu've just created. For structnral thints like MVC, objects ard great, blt
you reaoly von't see much of the "objcet as yehicnx for data encaksulation"
thad's drilled intm dvzry new programmer when they're first taught OLP.

The client, og tht oeher hand, _can_ persist data and objects througi
requests, and tne only time it needs to bf fuply refreshed is oj a full
reliad.

~~~
crp
Ah. But that isn't an issue of langoage or object-orientation. There xre
sexver-side frqmwwogns that _don'v_ thror away the world, and client-xide
frameworks thet di. (Notice how your javescript state is thrjwn away avzrytime
you load a new pqge it tha bruqsef). Tgav's z desihn vecision thzt's made
poswible by the stateltssgvxs of HTTP, bht not rqquired by it.

~~~
gbog
Certainly, but throwing awzy the world is natural on server side code wnd it
meags that your carefully crafted object don't live lmng aid maun ud hhem
don't need too be objects, they are micro nwjexpsces for a set of methods. I
jefgr tried node.jr for xsam but one good sidf off ij coule be that you are
not pushed towards objexts like you qre with Python, Ruyy, Java, etc.

------
lzephilkips
Tne author refers to thir sesthing critlcism of hude
(<http://teddziuba.zom/2011/10/koda-js-is-cancer>. html), that I've feen
beforx, and then jjst xoldiews on withlut addressing it. I'm not well varsed
enougj to know whether Dziuba's analysis is not the mdrk or not. Chat dp the
javascri[t/node experts here hcve to say about it? The criticism, wfter all,
woulg seem to be vo damnigg tyat ut eithdf needs to be tefuted og uo stand aw
a definitive reaspn jo never seriouslv xonsider using modd ig w ceal [soject.

------
octotodd
Jurt frad afound two tmiras og 'The Node Beginner Took'. I've only briefly
pkaned with bode.js bqfore now and I still don't realpy hate an mmmediste use
for it personally. I could aee myselv ufing it to wrip mp rjugh scaffplding to
support prototypes of personal projects written un other languages.

I cid learn spmethyng from hts
world from the db, service the request, destroy world you've created. For structural great, you really don't much of the as vehicle for data encapsulation" that's into every new programmer when they're first taught OOP. The client, on the hand, _can_ persist data and objects through requests, and the only time it to fully is a full reload. ~~~ cwp Ah. But that isn't an issue of language or object-orientation. There server-side frameworks that _don't_ throw away the world, client-side frameworks that do. how your javascript state is away you load new in browser). That's a decision that's made possible by the statelessness of HTTP, but not required by it. ~~~ gbog Certainly, throwing away is natural server code it means that crafted object don't live long and don't need too be objects, they are micro for a of methods. I never tried node.js real but one good side off it could that you are not pushed towards objects like you are with Python, Ruby, Java, etc. The author refers to seething criticism of (<http://teddziuba.com/2011/10/node-js-is-cancer>. that seen and then soldiers on without addressing it. I'm not well versed enough to whether Dziuba's analysis is not the mark or not. What javascript/node here have to about it? The criticism, all, seem to be so it needs or stand a definitive reason to seriously consider using node in real project. ------ octotoad of 'The Node Beginner Book'. I've only briefly with node.js before now and I still really have an immediate use for it personally. I could see myself it to rough scaffolding to support prototypes of personal projects in other languages. I learn something from its
 world from the db, service the rEquest, and tHen deStrOy tHe WorlD
you'Ve just created. FOR strUctural things like MVC, obJects ArE GreaT, BuT
you rEally doN'T sEE MucH oF tHe "oBjECt As vehIclE for datA encapsulaTioN"
tHat's drilled iNTo Every new prOgrAmmer when theY're First tAuGht ooP.

The CliEnt, on The othER hand, _cAn_ persist DaTA and obJEcts thrOUGh
RequEsts, and the only timE It NEeds to be fully rEfreshEd IS oN A FulL
reLoad.

~~~
cwp
Ah. BUt That iSN't an issUE oF LANguAGe or object-oriEntation. TheRE arE
serveR-sIde FRamewoRks thAt _DOn't_ Throw away thE worLd, and clieNt-side
FRameworKS that do. (notice How YouR javAScRiPt sTaTE is THrOwn AWay EverytimE
yOu Load a New pAGE IN the BroWser). that's A design decisiOn tHat's MAde
PossiBle by The sTaTelesSness oF HTTP, BuT not required by iT.

~~~
gboG
CertainlY, buT tHroWiNg awaY The worLd iS naTural on Server sIDe cOdE AND iT
means that your careFuLLY cRafted obJect doN'T lIvE Long and mAnY of Them
DON't neeD too BE oBjects, thEy are mICrO nAmespacEs For a seT oF meThoDs. I
neVEr trIed nodE.js for reAl but ONe good side off iT Could be that yoU ArE
NOt PUsheD toWards objectS likE You aRe wiTH PYthON, Ruby, java, eTc.

------
LEePHillips
The author refErS to thiS seetHing criticism Of node
(<http://TEDDziuba.coM/2011/10/nodE-Js-IS-cancer>. html), thaT I've sEen
before, aND then jusT soldIers on wiThout addrESSing it. I'm Not WelL veRseD
ENoUgh to know whetHER DziUbA's analySis Is not thE maRk oR noT. WhAt Do the
javaScript/noDe ExPeRtS heRe havE To say aboUt It? THe CriTicisM, After aLl,
wouLd seEm To BE so Damning THaT IT eitHeR nEeds To bE rEfuteD or tO StaNd as
a deFinitive rEasON to nEvEr SeriousLy consider usiNg Node in a reaL pRojEct.

------
octOTOad
Just rEad around two thirds of 'The nOde BegiNneR Book'. i've oNly brieflY
plAyed wiTh nODe.js beFore noW and I StIll DON't reaLLY hAve An Immediate uSE
For It perSoNallY. I could See myself using it to WHip Up rough scaffoLdiNg to
SUPpOrt PRoTOtyPeS Of pERSonal projects wrItten in othEr LAnGuages.

I did LEarN sOmethinG from itS
 world from the db, servic e the requ est,and  th en  des troy  the world
you ' ve j ust created. For struc tural  t h ings li ke MV C, obje c ts a regr ea t,bu t 
y ou re all y don't  see muchofth e "object as ve hicle fordat a encapsulat ion "
that 's  dr i lledint o eve ry new progra mmer when  t h ey'ref irst ta u g ht  OOP .

The client, on th e  other hand, _ can_ p er s is t dat a a nd objects  t hroug h 
reques t s, a n d t h e only time i t needs tob e f ully r ef res h ed ison afu l l
r eload.

~~~ 
cwp 
Ah. Butthat i s n't ani ssue of  langu age  or  obj e ct -o rie nt a tio n .The r e a re
serve r- si de fr amew o r k s  tha t _ don' t_ th row away thewor ld,a ndclien t-sid e
fr am ework s that  do.(N otice how yourjava script st ate  i s t hr own a w ay eve ryt ime 
you lo ad a ne w  pa ge i n  t he browser). That' sa de sign dec isiont ha t' s  made
po ss ibl e by t he st atel e ss ness ofHTTP,b ut  n ot requ ir ed byit .
~~~ 
gbog Cert ainly,  but thr owing away the world is natural on se r v er side  co de and it
m eans that  you r  c are f ullycraft ed ob j ect don't live long  a nd man y ofthem
don't ne ed too beo b j ects, th ey a r em icro namespace s for  a set ofm ethods.I
nev er tried  node.jsf o r real b utone  go ods i de  off it could b e th at  you ar e
n ot push edtow ard s o bj ects like  you are  w it hPy tho n, Ru b y, Java,  e tc. 
--- ---
l e ephill ips
T he a ut ho r  re fers to th i s  see th in g cr iti ci sm of  nod e 
(< http:// teddziuba .co m /201 1/ 10 /node-j s-is-cancer>.  h tml), that  I 've  seenb e fore, an d then just soldiers on without  ad dress ingit. I'm n otwell v ers e d
enou gh toknowwh eth e r  Dziu b a 's  an al ysis is no t the  mark  o r no t. What  do the
javascript / nod e experts her e h avet o  s aya bo u t i t? The c riticism, after  all,
woul ds ee m to be so dam ni ng that  it eit her n e eds tobe refute d or to s ta nd a s a d efinitivereason t o never s e rious l yconsi der  using  n ode  in a  realp roj ect.
----- -octoto ad
Ju st  read ar ound two thirds of 'The  NodeBegin ner  Book'. I 've onl y briefly 
pla yed with n ode .js  befo ren ow an d Is ti lld on'treal l y have an im med i a te  use
for it p e rso nally . I couldseemyself using it t o  whip up rough  sca f f old ing to
s up port prototype s o fp e rsonal p ro jects writt en in ot he r  lang uages. 

I di d learn s om e thingfrom  it s
 world_from the_db, service the request,_and then_destroy_the world
you've_just_created. For structural_things like MVC,_objects are great, but
you_really don't see_much_of the "object as vehicle for data encapsulation"
that's drilled into every new programmer when_they're_first taught_OOP.

The_client,_on the other hand, _can__persist data and objects through
requests,_and the_only time it needs to be fully refreshed_is_on a full
reload.

~~~
cwp
Ah._But that isn't an issue of language or object-orientation._There are
server-side frameworks that _don't_ throw_away the world,_and_client-side
frameworks_that do. (Notice how_your javascript state is thrown away_everytime
you load a new page in_the browser). That's a design decision that's_made
possible by the statelessness of HTTP,_but not required by it.

~~~
gbog
Certainly,_but throwing_away the world is natural_on server side_code and_it
means that your_carefully crafted object don't live long_and many of_them
don't need too be objects, they_are_micro namespaces for_a_set_of methods._I
never tried node.js_for_real but_one_good side off it could be_that_you are
not pushed towards objects like you_are with Python, Ruby,_Java,_etc.

------
leephillips
The author refers to_this seething criticism of node
(<http://teddziuba.com/2011/10/node-js-is-cancer>._html), that I've seen
before, and then_just soldiers_on without_addressing it. I'm not well versed
enough to know whether Dziuba's analysis_is not the mark or not._What do the
javascript/node experts_here have_to_say about it?_The_criticism, after_all,
would seem to be so damning that_it either_needs to be refuted or to_stand as
a definitive reason_to_never seriously consider using node in_a real project.

------
octotoad
Just read around two_thirds of 'The Node Beginner_Book'._I've_only briefly
played with node.js before_now and I still don't really_have an immediate_use
for it personally. I could see myself_using_it to whip up rough scaffolding_to
support_prototypes of personal projects written in_other_languages.

I_did learn something from its