The full stack of terminals explained
ludicrousdispla · 4 days ago
5 comments
ludicrousdispla · 4 days ago
5 comments
suzdude · 3 days ago
Anyone else get hit by the (now seemingly obvious) kernel --> shell naming while reading this?
paulddraper · 3 days ago
> In POSIX.1-2024, the master side is called “manager” and the slave side is called “subsidiary.”
Ah, who can forget the manager-subsidiary combo.
mkeeter · 3 days ago
> This is a clean separation, and clean separations are worth noticing. They tend to be load-bearing.
oh hi Claude
WD-42 · 3 days ago
> Three names, one thing. That’s why they blur together.
Stopped reading here. This is an AI article.
GlobalChubby · 3 days ago
Just to play devil's advocate: why? There's nothing a priori that suggests AI-written content is less pedagogically sound than human written content?
WD-42 · 3 days ago
Because the style is irritating, and as usual: if the author can't be bothered to write it, I can't be bothered to read it.
empthought · 3 days ago
We don’t need aggregators like HN pitching AI-authored content, no matter how pedagogically sound. We can direct our own AIs to generate our own AI-authored content.
paulddraper · 3 days ago
It's not necessarily less sound.
But it is a suggestion.
Human authors only write what they think is valuable. AI content lacks that signal.
JSR_FDED · 3 days ago
Thanks
beorno · 3 days ago
I made a website to be the caniuse for terminals, and it also includes some history/fundamentals stuff. I thought it was useful background if you want to dive into the capabilities of modern terminal and trying to make sense of the alphabet soup that is SGR, OSC, ANSI, etc:
https://terminfo.dev/fundamentals/tty-architecture