2 ms·
Implicit library loading isn’t even the real problem, it’s the global namespace. I think it, more than anything else, makes large projects difficult to manage d
by amarshall 2y ago
Implicit library loading isn’t even the real problem, it’s the global namespace. I think it, more than anything else, makes large projects difficult to manage due to the inability to grok the dependency graph.
- simoncion 2y ago> Implicit library loading isn’t even the real problem, it’s the global namespace. I'm not sure what you mean by this? Ruby gives you pretty much the same namespacing powers that most mainstream languages do. If your argument is that noone should EVER be able to hoist something into the global namespace, then I'm going to have to pretty strenuously disagree with you. Power tools are good to have for when you need them... but it's very important to have the restraint to only use them when you need them and leave them on the shelf when you don't.