Just because Microsoft used a particular IO abstraction in conhost and called it a “console” it doesn’t mean they’ve magically got full rights to that term and

Just because Microsoft used a particular IO abstraction in conhost and called it a “console” it doesn’t mean they’ve magically got full rights to that term and nor does it mean that established, industry recognised terms for that same thing suddenly don’t apply. I could release a book tomorrow and call it a “hippopotamus” but that doesn’t mean it’s not still a book. You get this all the time in IT, Chef calling their modules “recipes”, homebrew having “casks”, rust with its “crates”, etc. But that doesn’t mean they’re literally casks et al and no other established jargon henceforth applies. That’s just not how it works. However this is all moot because even Microsoft don’t refer to Windows Terminal as a console[0][1] and more does anyone else[2] apart from you it seems. 0: https://github.com/microsoft/terminal/blob/master/README.md https://github.com/microsoft/terminal/blob/master/README.md 1: https://www.microsoft.com/en-us/p/windows-terminal-preview/ https://www.microsoft.com/en-us/p/windows-terminal-preview/ 2: https://en.wikipedia.org/wiki/Windows_Terminal https://en.wikipedia.org/wiki/Windows_Terminal I get that you’re trying to use precise terminology but what you’re actually doing is over analysing things by making distinctions out of things that aren’t relevant.