3 ms·
> Would it really have been so terrible to leave the old directory alone and call the new one "Program Files (x64)"? Or alternatively, why was breaking them ou
by CydeWeys 9y ago
> Would it really have been so terrible to leave the old directory alone and call the new one "Program Files (x64)"?
Or alternatively, why was breaking them out required in the first place? To this day I frequently end up having to look in two places to find something, because it's never obvious which of the two Program Files it should be in. Pre-64-bit Windows there was only ever the one place. This is a permanent usability regression.
And of course, I wouldn't even need to be digging through there in the first place if the Start menu launcher just worked, but no, they had to junk it up with Cortana, which is so incompetent it can't even find installed applications by name. More details on my Cortana rant here: https://news.ycombinator.com/item?id=15758641 https://news.ycombinator.com/item?id=15758641
- njovin 9y agoI absolutely agree with this. There should have just been a 'Program Files' folder and if a conflicting program was already installed, the architecture could be appended to the name of the newer install's directory (C:\Program Files\Foo, C:\Program Files\Foo (x64)).
- pjc50 9y agoI tried to find an authoritative answer from Raymond Chen, and the closest I can find is https://blogs.msdn.microsoft.com/oldnewthing/20081222-00/?p=19763 https://blogs.msdn.microsoft.com/oldnewthing/20081222-00/?p=... and linked http://brandonlive.com/2008/12/22/why-does-windows-put-64-bit-binaries-in-system32/ http://brandonlive.com/2008/12/22/why-does-windows-put-64-bi...