The full stack of terminals explained

Discussion (9 Comments)Read Original on HackerNews

beorno•42 minutes 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

mkeeter•about 3 hours ago

> This is a clean separation, and clean separations are worth noticing. They tend to be load-bearing.

oh hi Claude

suzdude•about 4 hours ago

Anyone else get hit by the (now seemingly obvious) kernel --> shell naming while reading this?

WD-42•about 3 hours ago

> Three names, one thing. That’s why they blur together.

Stopped reading here. This is an AI article.

GlobalChubby•about 2 hours 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?

empthought•about 1 hour 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.

WD-42•about 1 hour 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.

JSR_FDED•about 2 hours ago

Thanks

paulddraper•about 3 hours 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.

The full stack of terminals explained

⚡ Community Insights

Discussion (9 Comments)Read Original on HackerNews