Is that why sometimes Edge queues up UI actions while pages are loading? Having stop and back and whatnot wait to be processed until whatever stuck thing gets unstuck isn't exactly what I had in mind.
Do you mean this would be their most major impact? The link you posted below is for Edge 15 and not for chromium.
But in chromium the scheduler should already be handling input off the main thread when possible.
Otherwise agreed with the point that this article is weirdly focused on a single somewhat underwhelming change when there have already been a bunch of changes.
I'm confused by these statements (not just yours but in the article as well) about how Edge performs so well; I have not seen anything like that on the Windows 10 systems I am forced to use (for work). On those systems Edge takes forever to load, forever to open a new tab, and will randomly make the mouse cursor disappear when it's doing something it considers more important than responding to my input.
I thought it might be that, but it so happens we had to get a Windows 10 machine for home use for a particular purpose, and Edge on it is also slow (though perhaps not quite as slow as my work machine). Both are Dell laptops, so it's possible that Dell puts some extra OEM stuff in that hurts performance.
I think I have seen that disappearing mouse issue though, and mostly I use Edge when I double click on a PDF file and forget I don't have a PDF reader installed....
Wonder how annoying the switch to chromium will be :/
The use case for perf improvement with async/await is for IO based issues, eg instead of burning a thread waiting for IO to complete, use IO completiion ports (on winders) blah blah.
If your work is CPU bound you can't async/await it away magically.
Maybe I'm misunderstanding you?
Side note, this is why I’m a huge fan of Qt. They really did a fantastic job on building that framework for c++ to make it more safe
It's similar to using an event loop architecture for all UI actions.
This would allow chrome to have lower input lag than native GUIs if it's not already the case.
They are also working on many cool things, openXR support for example. They are improving chrome devtools (and their integration within vscode) They are doing many performance related fixes. And they are massively modernizing windows apis used by Chrome. E.g better performance for sensors through new windows 10 API. And the smart use of a Kalman filter for sensors.
They are also helping chromium to support windows ARM 64 bit
A real time view of what they are doing: https://chromium-review.googlesource.com/q/author:*.microsof...