>But so do the global objects, whose properties replace them. The danger of an accidental local/private var tampering with it is nil, but this global object's methods are avalilable everywhere around the app. Any nasty routine can approach it and either mess with its properties, or call its methods to do the same. So, globar vars are bad news, for sure, but we got to beware of global object abuse as well. Still, these are easier to find... well, it would be, if we had the Filer the way it was.
>

Global object properties cannot be referenced without using the global object's name. This prevents a lot of misuse. But my comments are more related to the variable reference to the global object and the fact that that variable doesn't need to be public for the object to be global.