|
|
|
|
|
|
by easton
1712 days ago
|
|
|
Not that your IT department will be letting you update today, but something to look forward to is that Teams in Windows 11 uses the shared Edge WebView runtime (replacing Electron), which means it takes around 50% of the RAM it did in Windows 10. Also, WSL graphics support (which isn't coming to Windows 10 for some reason), winget has been moved to stable (that is coming to Windows 10), and Windows Terminal is included in the box (but doesn't replace the cmd.exe or powershell.exe terminal emulator for some reason). |
|
|
Windows has a console interface unlike that found on Unix, using APIs rather than escape sequences to interface with the console. Also, its console implementation was historically coupled tightly with the conhost.exe application, which historically is both the terminal emulator and console endpoint simultaneously.
The blog series centered around https://devblogs.microsoft.com/commandline/windows-command-l... is the best resource I've found online that discusses Windows' legacy console support as well as some vision of how this subsystem has changed in the years since.
These changes improved OS interop, but also de-couple the legacy crap so that third party terminal emulators can be better supported on Windows generally (separating the console endpoint from the terminal display), allowing for the creation of `CreatePseudoConsole()`.
Prior to this, third party terminal emulators that wanted to support Windows apps had to run the legacy conhost.exe and shove the window way off the desktop (to hide), and then scrape the window for its contents. This is/was required so that the app has a console backed by a conhost.exe process (responding to the console apis). `CreatePseudoConsole()` fixes a lot of that mess.