>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+.
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.
I thought "eats RAM" meant it had a memory leak. Not that its memory usage is 1GB high.
This fix sounds more like a hack. Effective, but not a long term solution, and it has negative effects like the firewall.
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.
Microsoft Teams eats RAM. Period.
>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+.
> 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.