The new stuff is faster, but it also eats more specs.
Microsoft released a new version of the Copilot update on Windows 11 with significant changes to the structure of the app. From the original native development, WinUI was adapted to a web-based app instead, which resulted in both functional and resource use.
.
When the app switches to web-based, the main engine will be WebView2, which works with Microsoft Edge, allowing the app to run the web-based UI (web. copilot. com) directly.
.
In terms of practicality, it was found that the face and experience were hardly different from the web version of Copilot, with the entire interface being rendered through WebView2, while behind the scenes there was an Edge instance working together, giving the app a certain degree of fluidity, but at the expense of a noticeable increase in resource consumption.
.
The point is that this new version does not use the normal WebView that relies on Edge in the system, but a full version of Microsoft Edge is bundled into the app, making the activation time almost like opening another browser, resulting in an increase in RAM consumption below 100MB to around 500MB, and perhaps reaching 1GB during use, along with clearly higher CPU usage.
.
Technically, the structure of the new app is a hybrid between WebView2 and the full browser, with both WebView and Edge runtime bundled in one, unlike regular PWA or WebView-type apps that often rely on the engine available on the system.
.
The overview of this change reflects Microsoft's approach of trying to bring the Copilot experience closer together on all platforms, using the Web as its core. While it allows faster feature development and updating, it comes at the expense of performance and use of machine resources.
.
Source: HKEPC






























































































