Hacker News new | past | comments | ask | show | jobs | submit login

Probably because PATH variable was considered deprecated. You are supposed to put paths to your executables in the registry:

https://msdn.microsoft.com/en-us/library/windows/desktop/ee8...

> We recommend registering your application in the App Paths registry subkey. Doing so avoids the need for applications to modify the system PATH environment variable.

http://blogs.msdn.com/b/oldnewthing/archive/2011/07/25/10189...

> On top of the difficulty of adding more directories to the PATH, there was the recognition that this was another case of using a global setting to solve a local problem. It seemed wasteful to add a directory to the path just so you could find one file. Each additional directory on the path slowed down path sarching operations, even the ones unrelated to locating that one program.

> Enter App Paths. The idea here is that instead of adding your application directory to the path, you just create an entry under the App Paths key saying, "If somebody is looking to execute contoso.exe, I put it over here." Instead of adding an entire directory to the path, you just add a single file, and it's used only for application execution purposes, so it doesn't slow down other path search operations like loading DLLs.




Would be nice if cmd and powershell also looked in App Paths allowing to be an actual replacement for %PATH% (without having to do "start app.exe")




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: