Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Global namespace clobbering has huge implications. With modules/namespaces you have a well defined and limited blast radius: a change is limited to a module and calling code.

Now, imagine your environment of choice supported dynamic runtime loading of code where the code is just dropped to the global namespace. This screams "insecure" and "how do I know if I call the code I want to call?".

Now imagine the only mitigating mechanism was `include_once`. It would make sense software written in this environment requires own CVE namespace as new security vulns are discovered every second



What he wound up arguing for was that everything would have a globally unique name.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: