Yep .. so if you want a rich responsive user experience, DON'T use any web technologies. GMail (AND Gsuite) is a perfect example of how a relatively simple concept like email can be turned into a slow, unresponsive piece of garbage.
PS4 feels like they've taken webtech all over the OS interface. Its store's snappier than the 3 but the rest of the interface performs way worse. Usable, but far less pleasant.
[EDIT] store should be snappier than the 3, mind, since it's way more powerful hardware—it's still kinda slow, considering.
STBs, Smart TVs, IFE systems are or were web based.
One of the main drivers for getting a amazon fire stick is that it is much more responsive than the Smart TV itself.
GMail is a poorly built app, that's all. There are plenty of great examples. Both Outlook and Fastmail have fast and feature-rich email clients. Gmail was good back in the day and got carried away by project managers and feature creep.
Meanwhile Google Docs continues to be a pinnacle of what you can achieve on the web.
Reality has rtt and shitty 2G slow, and will drive people away from your web product if you are too silly to cache things locally.
Also I find most performance issues with big apps are a result of browser extensions that interfere. Try using a private window without any extensions.
Says the OS developer, says the browser developer, says the webapp developer, says the developer of whatever else you have running. Developer time is expensive. Says one. Look it runs fine and is snappy. Says another on his maxed out development pc forgetting about his grandma. Why should i care about that extra memory load when most pc's nowadays have x amount. Says yet another.
And so the slugfest continues.
>Also I find most performance issues with big apps are a result of browser extensions that interfere. Try using a private window without any extensions.
Browser extensions can definitely make a browser sluggish but most don't interfere with the content. The only ones that do AND are common are adblockers which have a tendency of making it less sluggish.
(1): burning through an SSD's limited number of write cycles OR being at least an order of magnitude slower to access in the case of HDDs
Bloat RAM is also wasted RAM. If it's not being used as a cache of reasonable size, or in a time/speed tradeoff, all you're doing is making things worse.
> If you don't have anything else that needs it then just let your system automatically handle it.
That's a statement that only really applies to people misunderstanding RAM used by the page cache or suspended programs. And both of those depend on active applications not allocating that memory!
Probably because that RAM wasn't doing anything else. Why not use it as cache to speed things up. I'm sure it can work fine in much smaller RAM sizes.
And that doesn't explain how the "cache" is twenty times bigger than the source data.
I bet with less RAM available it would start thrashing.
How do you think that would have worked for Gmail's success?