3 ms·

Microsoft didn't invent consoles. They have also been around longer than Microsoft have existed. The distinction you're making here is pretty tenuous and irrele

Microsoft didn't invent consoles. They have also been around longer than Microsoft have existed. The distinction you're making here is pretty tenuous and irrelevant to the original question being asked since we're talking about the terminal GUI not the console guts; and the fact that Microsoft even call this product "Windows Terminal" should make this an open and shut case.

JdeBP 7y ago
Microsoft did invent this particular I/O abstraction, named a console. And it's only irrelevant if you disagreeing with "Windows Terminal is a console" is irrelevant. Were you irrelevant? (-: Windows Terminal is built on top of the console I/O mechanism. It talks to consoles, as do the 1990s and later Win32 console applications that one can run displayed within Windows Terminal. Arguing with someone who says that "Windows Terminal is a console", as you did, based upon the product name is fairly flawed. The name for this I/O abstraction, invented by Microsoft for Windows NT and evolved from earlier operating systems, is a console. If you want open and shut, by the way, one of the programs that is the innards of Windows Terminal is named OpenConsole.exe . It provides an enhanced implementation of the console I/O server, formerly conhost, and before that formerly CSRSS.
- laumars 7y ago
  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.

JdeBP 7y ago

Microsoft did invent this particular I/O abstraction, named a console. And it's only irrelevant if you disagreeing with "Windows Terminal is a console" is irrelevant. Were you irrelevant? (-: Windows Terminal is built on top of the console I/O mechanism. It talks to consoles, as do the 1990s and later Win32 console applications that one can run displayed within Windows Terminal. Arguing with someone who says that "Windows Terminal is a console", as you did, based upon the product name is fairly flawed. The name for this I/O abstraction, invented by Microsoft for Windows NT and evolved from earlier operating systems, is a console. If you want open and shut, by the way, one of the programs that is the innards of Windows Terminal is named OpenConsole.exe . It provides an enhanced implementation of the console I/O server, formerly conhost, and before that formerly CSRSS.

laumars 7y ago
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.