Absolutely. But that's a universal issue with JavaScript OO in that it provides no direct language support for encapsulation. Developers have, for the most p

Absolutely. But that's a universal issue with JavaScript OO in that it provides no direct language support for encapsulation. Developers have, for the most part, learnt to be disciplined about not accessing "private" fields in JS objects. That they (we) have not learnt to apply that lesson with respect to class hierarchies is evidence for how willingly we throw away good principles when we are working in a "special case". It is also a lesson in why having language features that force developers into good practices is sometimes a net win, even though we might also rally against them (because we dislike their verbosity and/or hand-holding).