The GP makes a valid point - that conditioning explains the expectation of a situation that an enlightened person would call abusive - with an admittedly ripe analogy.
Yes, it's wrong. Application data should be separate from user data. It's a necessity in a multi-user OS.
I do want my data to remain intact across application upgrades and reinstallations.
I probably do not want to apply the same backup policy to my installed applications as to the data I create with them.
I'm just your average user, not a developer. Intuitively, when something is saved, especially something like a game save, I EXPECT it to be written to the game's fucking application directory.
This is wrong. With the huge installation sizes of modern games, I know of many average users (especially purchasers with original media) who uninstall and reinstall their games and appreciate when their saved games persist.
And why shouldn't they? Save game files tend not to be terribly big, and if I can't have 3 20GB games installed at the same time why should I have to start again every time?
These same average users are bothered by the presence of a old game folder in Program Files after uninstallation (me too!) - "Why didn't it uninstall completely?".
The answer to this is invariably that the uninstaller was not able to remove some files that were created in the application directory. And that's because they shouldn't be there.
The original ranter was bang on point.