3 ms·

It seems clearer but when you install wamp or xampp you'll find a php.ini in c:\wamp\apache and c:\wamp\php (or sthg). Nice names (be it /etc or C:\Users) don'

It seems clearer but when you install wamp or xampp you'll find a php.ini in c:\wamp\apache and c:\wamp\php (or sthg). Nice names (be it /etc or C:\Users) don't prevent developers to put their config file wherever they can read it. Usually in C:\Users\Alice\Ubisoft if they are in the game business. Or C:\Program Files\Steam\Steamapss if they are in the game business.

wvenable 11y ago
Talking about where PHP (a unix program) puts it's configuration on Windows is hardly a valid point. Even on Linux, that sucker can be hard to find. On my Linux server it is at least 5 levels deep and I have to run phpinfo() just to find it.
- johnchristopher 11y ago
  > Talking about where PHP (a unix program) puts it's configuration on Windows is hardly a valid point. That's because it's not my point but an example of "it's up to the dev to be consistent or to follow the platform's guideline" which is my point along and with "`Program Files' is a nice folder name but you are going to find some user configuration files in there'". If I remember correctly Foobar asks you when installing where to put its configuration files: user home, or program files. It should not. It should be in C:\Users\Alice\Local Settings (or was it LocalApps ?).
  - chinpokomon 11y ago
    There are guidelines for where developers are supposed to store configuration, and since Vista, it isn't in Program Files. In fact, making changes in Program Files is restricted to the System, or elevated processes. It is often times an indicator that a program is violating accepted practices if it requires elevation of privilege to run. Changes like that are supposed to be stored in the users AppData directory. For backwards compatibility. Vista and descendants provides a virtualized space where writes to restricted directories are allowed, but they are committed to a different isolated space on the disk, preventing a rogue program from, modifying files for which it should not have access. Neither Windows or Linux are perfect in this respect, but for a decade, Microsoft has been trying to unify how applications store user specific data and configuration. There are still ways for developers to abuse the system, but they are considerably restricted from the most glaring mistakes and in general it has gotten better with each revision.
- deleted 11y ago
  [deleted]

wvenable 11y ago

Talking about where PHP (a unix program) puts it's configuration on Windows is hardly a valid point. Even on Linux, that sucker can be hard to find. On my Linux server it is at least 5 levels deep and I have to run phpinfo() just to find it.

johnchristopher 11y ago
> Talking about where PHP (a unix program) puts it's configuration on Windows is hardly a valid point. That's because it's not my point but an example of "it's up to the dev to be consistent or to follow the platform's guideline" which is my point along and with "`Program Files' is a nice folder name but you are going to find some user configuration files in there'". If I remember correctly Foobar asks you when installing where to put its configuration files: user home, or program files. It should not. It should be in C:\Users\Alice\Local Settings (or was it LocalApps ?).
- chinpokomon 11y ago
  There are guidelines for where developers are supposed to store configuration, and since Vista, it isn't in Program Files. In fact, making changes in Program Files is restricted to the System, or elevated processes. It is often times an indicator that a program is violating accepted practices if it requires elevation of privilege to run. Changes like that are supposed to be stored in the users AppData directory. For backwards compatibility. Vista and descendants provides a virtualized space where writes to restricted directories are allowed, but they are committed to a different isolated space on the disk, preventing a rogue program from, modifying files for which it should not have access. Neither Windows or Linux are perfect in this respect, but for a decade, Microsoft has been trying to unify how applications store user specific data and configuration. There are still ways for developers to abuse the system, but they are considerably restricted from the most glaring mistakes and in general it has gotten better with each revision.
deleted 11y ago
[deleted]