I agree, the point is more that if you're going to write OOP JS **with inheritance**, then prototypes are nice because they are the standard way. My point is NOT that "functional is terrible", it is that if what you want is OO with inheritance, then please use the capabilities the language provides. I'm sick of seeing people write yet another mutually-incompatible class system to implement OO. I wasn't really writing that chapter for people who are already well-versed on the functional style :)
On Tuesday, June 19, 2012 3:27:12 PM UTC-7, Nuno Job wrote: > > Do functional style if you feel like it, OO if you feel like it. > > It's your choice, nodejs lends itself to both. > > A lot of good nodejs developers do OO. A lot of good nodejs developers do > functional style. > > Ignore FUD, and all the benchmarks that consistently look at non > bottlenecks. > (If you are creating 1 million objects per second you are probably doing > something else wrong) > > Nuno > > On Thursday, September 29, 2011 8:30:07 AM UTC-7, Giovanni Giorgi wrote: >>> >>> Hi all, >>> I am new to nodejs, even if I am a 37 super-nerd loving programming >>> languages. >>> >>> I know and love python, java, ruby, erlang, SmallTalk, bash, emacs-lisp >>> (less then other :-), coffescript, perl, Self and so on >>> >>> So I started to play with nodejs, too which was not yet in the "web >>> framework" collection of mine :) >>> >>> I have always OOP in python, Self and SmallTalk. >>> Making objects is fun. >>> >>> But after reading >>> >>> https://github.com/**spencertipping/js-in-ten-**minutes<https://github.com/spencertipping/js-in-ten-minutes> >>> >>> in particular "5.1 Why new is awful" and "5.2 Why you should use >>> prototypes", a lot of things in my head went wrong. >>> >>> I fear strong-OOP is not the better way of code in JavaScript and in >>> nodejs in >>> particular. >>> >>> Nodejs is callback-based. So a functional approach is better, and >>> should I avoid using class >>> inheritance? >>> >>> I like functional approach, but in my little experience it works quite >>> bad with high dynamic >>> languages, and javascript oddities seems not a good starting point. >>> >>> What is your experience (and suggestions)? >>> >>> --- >>> Gio's Blog http://gioorgi.com >>> >>> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> > > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
