Re:Microsoft admits Teams eats RAM on Win doing nothing, and...
by ksec on Sunday December 28, 2025 @04:03AM
(#46409575)
>Microsoft really needs to dump WebView2 and go back to native code
And then a screenshot showing 213MB even in native code.
How that happened in the past 25 years? I know we have Higher Res graphics and renedering but it is absolutely insane to see Apps, and those on the phone being 500MB+.
Re:Microsoft admits Teams eats RAM on Win doing nothing, and...
by hulitu on Sunday December 28, 2025 @07:56AM
(#46410746)
> How that happened in the past 25 years?
You know Crysis, the game that couldn't run properly, even with the latest hardware ? _That's _ what happened in the past 25 years. Nobody gives a shit about resources. Hopefully the RAM prices will fix some things.
And then a screenshot showing 213MB even in native code.
How that happened in the past 25 years? I know we have Higher Res graphics and renedering but it is absolutely insane to see Apps, and those on the phone being 500MB+.
You know Crysis, the game that couldn't run properly, even with the latest hardware ? _That's _ what happened in the past 25 years. Nobody gives a shit about resources. Hopefully the RAM prices will fix some things.
It is almost guaranteed that people will not be able to call, due to firewall blocks or process not running or some other issue.
It feels kind of strange to pull the main feature/usecase of your application out of your application. I would reconsider my design by then.