5 ms·
It just baffles me how many apps that would have been fundamentally doable on a 486 with Windows 3.1 and 14.4 dial-up somehow manage to gulp resources on modern
by PhasmaFelis 10y ago
It just baffles me how many apps that would have been fundamentally doable on a 486 with Windows 3.1 and 14.4 dial-up somehow manage to gulp resources on modern machines.
(Although, for 1 and 2, it seems like temporarily closing the Slack app would work just as well.)
- antod 10y agoAt my first job, a machine of that spec was a typical AutoCAD workstation (although some still ran DOS). The really grunty DX50s even had 16MB of RAM (whoa).
- _asummers 10y agoNo part of me wishes computers were limited like they were then, I just wish software in general didn't assume it was the only thing running on someone's machine and was not so cavalier with resource usage.
- shinymark 10y agoIf Slack's desktop client was written in efficient C++ using platform specific UI framworks it would likely be one to two orders of magnitude more efficient across all important metrics. Unfortunately the desktop app is basically an entire web browser instance running JavaScript code. I can see the appeal, however. Write once run anywhere is a hell of a drug.
- TeMPOraL 10y ago> I can see the appeal, however. Write once run anywhere is a hell of a drug. It's not just that. It's that you're not paid to write good code, nor efficient code. You're paid to write any shit that works good enough to be sold to users, and to write it as quickly as you can.