> So the problem isn't the autoloader, but Ruby's and PHP single global namespace. Interesting point and I agree! The thing I like about python and javascript

> So the problem isn't the autoloader, but Ruby's and PHP single global namespace. Interesting point and I agree! The thing I like about python and javascript's import system is you import the object that you end of using, creating a namespace as a variable, defined at the top of every source file. This lends itself to traceability which was my primary argument in the post. I can see how I conflated the global namespace in ruby with automatically loading classes. Cheers!