3 ms·
So they're not actually doing anything with the pile of garbage webviews they base their chat on? Darn. It'd be nice to export conversations to text files from
by WWLink 5y ago
So they're not actually doing anything with the pile of garbage webviews they base their chat on? Darn. It'd be nice to export conversations to text files from the client side, or at least be able to, ya know, RELIABLY COPY AND PASTE MORE THAN 1 MESSAGE AT A TIME.
And then heaven forbid I need to scroll more than a little bit.
This doesn't sound like it solves ANY of that. They just changed the rendering engine. Whoopdeefuckingdoo.
- laumars 5y agoChrome is pretty resource heavy and Teams might not need all of that. Eg It might not need the latest web APIs or even v8 at all. While it seems counterintuitive, I have read quite a few success stories of people moving from Electron to Qt Webviews. Obviously fully native would be preferable from a user experience but at least with a webview you can start to build hot paths in C++/Rust/etc more easily than one might be able to with Electron. So this might not solve all of Teams desktop application problems it’s still a step in the right direction.
- mcny 5y agoI was thinking the same thing - why does teams need multiprocess / electrolysis to use a Firefox terminology...
- SuchAnonMuchWow 5y agoand the rendering engine is still based on chromium underneath ...
- Smar 5y agoDoes it even change the rendering engine? Rather changing to another flavor of same engine.
- deleted 5y ago[deleted]