4 ms·

Marginal gains. 50MB here, 100MB there ... pretty soon you're talking real storage usage.

• hirsin 7y ago
  Pretty much this. I once tried adding a new ~3 MB binary, and it was rejected on effectively these grounds. Now consider that the team making these in/out decisions has a backlog of requests just like it for larger items...
  • pas 7y ago
    Is there a team that can exterminate other teams in very medieval ways that fail to make stuff installable to non system drive? Because there should be. It's crazy that everything still wants to put stuff on C:\ ... I'm looking at you Visual Studio and Win SDK. Plus Users\Public shared goodies. And the %userprofile%\AppData. I get that every application thinks it needs to put its cache/files there, but then why can't folks relocate users' homes? :/
    • TeMPOraL 7y ago
      > Is there a team that can exterminate other teams in very medieval ways that fail to make stuff installable to non system drive? I'd love if that team would also take a look at Android, where you simply can't not install on the "system drive" aka. main phone flash.
      • hirsin 7y ago
        That was a design decision made because install to SD card causes apps to load slowly (to my understanding). It used to be possible but they killed it. Doesn't hurt that it helps speed up the upgrade cycle since users run out of on-board space sooner.
• marcosdumay 7y ago
  Some 10 of those and it makes some difference on a phone... In how many places does Windows concentrate the settings for everything?
  • philjohn 7y ago
    3 in this case ... registry, registry backup and system restore points. Makes sense to get rid of one of those, especially as restoring a registry backup can lead to unintended issues if you've installed something since, whereas a system restore point takes care of all of that for you.