4 ms·
> Automatically unzips into %ROAMING% blame MS for that garbage > 140 MB of RAM used wow, that would be alot in the 90s
by amcca029 9y ago
> Automatically unzips into %ROAMING%
blame MS for that garbage
> 140 MB of RAM used
wow, that would be alot in the 90s
- pikzen 9y ago> blame MS for that garbage Uh... As far as I know, installers work well. Sorry for wanting to choose where I install my stuff. Spoiler: It's not on C:\. Chrome started that trend of install-less installs, and I've hated it ever since. >wow, that would be alot in the 90s Indeed, let's see which processes I have running that take up less than 140MB, shall we? * Battle.net. Full app launcher, with patching capabilities, okay. * OpenHardwareMonitor. Does a shitton more than GitHub. * Mumble. Does a shitton more than GitHub. * Windows Explorer. Does a hell of a shitton more. * Steam. Finding a pattern there? * Origin. Skype. Task Monitor. Intel XTU. The list goes on and on. All doing infinitely more than what amounts to little more than an UI on git.exe Thing is, sometimes I actually need that RAM. To run games, Photoshop, or Atom, depending on how much I hate myself right now. But hey, it's okay, as a developer, you can choose to disrespect your users, that's your choice, not mine :>