3 ms·
In my experience, making obviously bad things difficult or impossible improves reliability. This idea certainly resides within my cranial cavity, but that doesn
by DanWaterworth 14y ago
In my experience, making obviously bad things difficult or impossible improves reliability. This idea certainly resides within my cranial cavity, but that doesn't necessarily make it wrong.
- jlgreco 14y agoHow could: HashMap = HashTable = Map = Table = Dictionary = Hash possibly not qualify as "obviously bad"? The only reason you've offered up is because it is easy...
- DanWaterworth 14y agoI think this is fine. The obviously bad part is being able to remove/change constants, especially as these changes are global.
- agscala 14y agoThe obviously bad part is that you pollute the global namespace for no reason other than laziness. When someone comes across code that uses a "Table" object interchangeably with "Dictionary" and "Hash", then he's going to have to look through the source code to find this bizarre line only to find out that you renamed a built-in container for no good reason.
- DanWaterworth 14y agoYes, I suppose that's also true.