3 ms·
> Until this article, I always blamed this on the decision to blindly import modules instead of... well... whatever makes sense. Now I'm realizing if we all avo
by diggan 2y ago
> Until this article, I always blamed this on the decision to blindly import modules instead of... well... whatever makes sense. Now I'm realizing if we all avoided common names for packages then there would not have been an issue.
If your solutions depends on others to "do the right thing", it often isn't a viable solution.
However, how you import something in your own files, is something you most likely control.
- riskable 2y agoHaving a global style policy (for imports) doesn't seem like relying on others to "do the right thing". It's just style and is completely arbitrary. Someone probably encountered a problem with having a mishmash of ways people do imports and thus began the policy. It's the type of policy where someone heaved a great big sigh and said, "this is why we can't have nice things."
- diggan 2y agoI was specifically referring to the "Now I'm realizing if we all avoided common names for packages then there would not have been an issue" part as relying on others to do the right thing. Having a internal policy about how to import something wouldn't be relying on others to do the right thing.