> Bottom line is, the global holds information about something... that sounds like the property of an object to me... if there is no abstract of the object in your ap, perhaps you should create one! A class!

I agree with you in principle, but as a matter of practicality, I've seen the properties of application objects proliferate to unwieldy proportions too many times to count. In a lot of cases it may be for preferences, system wide view parameters, etc. In almost all cases it would probably be best for these properties to exist as properties of another object somewhere, but when global access to them is required you're then left with having to either know how to reference the object from anywhere or making the object public.