On Fri, Mar 16, 2012 at 4:18 PM, David Bruant <[email protected]> wrote: ... > This is a piece of cake with Java's protected. It is much convoluted in > JavaScript. I think this kind of problem being hard to solve in > JavaScript is the reason why so many frameworks like Node.js make the > choice to expose their internals.
I doubt this is the reason. Many JS devs recognize that private/protected are great for the 1% programmers who work on clearly defined, simple problems. Predicting what needs to be exposed and what does not in real problems is hard and fails. This extract a cost in real projects. The benefits of private/protected are exaggerated, as can be clearly demonstrated by admiring the success of languages without it. I'm not saying private/protected is a bad thing, I'm only disputing your conclusion. jjb > > David _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
