Item — HN Reader

That is why I said the 2x improvement about Webview they said earlier doesn't matter. And I believe the 10sec already accounted for the 2x improvements.

>the new Outlook uses between 490 MB and 636 MB of RAM while idle, with individual sessions varying based on mailbox size. Outlook Classic, doing the same job, uses around 117 MB to 148 MB at idle. A roughly fourfold difference.

In the old days, we would have cried about 150MB memory usage idle as being bloat. Why isn't it 30 to 60MB. Now 150MB is still so much better than 600MB.

I am not sure if Native will ever win. I do wonder if we could somehow make webview, or may be a subset of webview that is as fast as native.

1 comments

> In the old days, we would have cried about 150MB memory usage idle as being bloat.

I'm curious how much of those 150 are things that can't be boiled down to 'text', since that should be roughly the same size as on completely un-bloated software. The database of emails, the plain text of said emails, and all the basic UI should all be nothing but text and take up next to nothing.

Images on the other hand. I'd imagine Outlook Classic hasn't been made with 1 MB PNGs for all their icons, so it's probably not that that's pulling the memory usage, although it's probably contributing. Meanwhile, New Outlook (New) probably didn't optimise a single thing, so it probably is using 1 MB icons, which then quickly piles up. Not to mention the whole webview rendering backend, since we apparently can't make anything without going through a few layers of abstraction first.