> > > I would recommend having those listed features in mind when talking about > super() and namespaces, because the current spec still will prevent me from > using native "class" keyword in JavaScript. > > If newbies ask me if they should use classes, I say no to them, because I > still think the featureset of a mixin-based inheritance (leading to fancy > prototype copying and sealing) is still better. >
That would be terrible advice, because classes in Javascript are just sugar for setting up a constructor and its associated prototype. Once you define a class, you can do any kind of dynamic tomfoolery that you like, including setting up mixins in the fashion you describe.
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
