Module Pattern Provides No Privacy... at least not in JavaScript(TM) (via) JavaScript variables hidden inside a closure aren’t as hidden as I thought—it turns out you can pass a closure as the second argument to eval (at least in Firefox) and “steal” private variables back out of it.
Sign in with 
OpenID
Maybe the important thing in any programming language is to discourage bad practices, rather than going out of your way to forbid them absolutely. To quote from "Programming Perl",
"A Perl module would prefer that you stay out of its living room because you weren't invited, not because it has a shotgun."
Trying to prevent people from frobbing your code seems like a rather Sisyphean task. Are folks actually trying to secure data using the Module pattern?
If not, it seems like this is one place where I would agree with GvR. We're all adults here, please don't come crying when your code breaks because it calls implementation APIs.