I cannot talk about others, every human has responsibility over their own knowledge and understanding. But I can talk for myself and I don´t stop thinking only because someone use the class word. I trying to see features and behaviour, and this behaviour is specially bound to the word "class" and "OOP". I choice to use the helper because:
- It makes the code more simple to read, if you ask me. - It will generate a optimized class function which will be very fast and have low memory usage. - It can implement optional options which allows cache long deterministic methods calls. - It can implement helpers, like parent "class" with a little cost (compiler option) - Better encapsulation - If you speed up the "Class" function generated, will you speed up every instance of it. - Automatic generate methods, like default constructors, setters, getters, and mix-in behaviour. - Add "destructor" and therefore allow some light RAII, which is in my opinion the right solution to solve resource leaks. - It is 100% compatible with every hard coded class function, I can use it together with any existing "class" function. By using your arguments would it be equal to say it is stupid to abstract away things to be able to look at something on a more higher level. Functions was made for this task together with code reuse. You would´t normally write the same code twice but create a function for it, but when the same thing for "class generation" is it suddenly a "confrontation with the language", even I use the most powerful feature of the language? I simply don´t agree. Den måndagen den 12:e november 2012 kl. 15:01:58 UTC+1 skrev greelgorke: > > i would use your helper if i would contribute to your projects, and hell, > yes i would contribute to your projects, if i had time and interest on the > topics there. but i also would ask you, why do you use such a helper and > try to trigger your thinking about it as well :). > the worst thing is not that people use class-emulating helpers and libs, > the worst thing is when they do it to avoid the confrontation with the > language and it's internals. ignorance is the enemy, not tools. you said, > one has not to be an expert, but a knowledge about fundamental concepts of > the language is crucial. But many some developers just see "Class" and > shutdown exploration mode in their brains, asume a paradigm, that isn't > there, and wonder then, why JS is so lame. > -- 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
