3 ms·
Well this is exactly the point that people disagree on with me. I think your application owns the global namespace, as long as your dependencies are neatly defi
by tinco 12y ago
Well this is exactly the point that people disagree on with me. I think your application owns the global namespace, as long as your dependencies are neatly defined somewhere there really is no downside to letting pulled in libraries 'pollute' your global namespace.
- marknutter 12y agoWhen you're working on large teams it's no longer your global namespace alone. I've worked on quite a few projects that abused the global namespace and it's very painful to try and recover from.