> Why a TUI is the best thing we pipe through ssh?

`ssh -XC` (look up SSH X forwarding). You can also easily tunnel remote desktop over ssh.

> Why I cannot watch a 4k movie in the terminal or browse the web using pinch to zoom ?

Kitty, sixel, and iterm2

It's not 4k, but ssh to funky.nondeterministic.computer if you're using a modern* terminal emulator program. (aka ghostty)

A terminal UI is the best thing we pipe through SSH because it's the tool we built specifically for piping a terminal UI. Abandoning Xorg has admittedly made streaming a GUI over SSH less simple, but still not impossible, and you can forward whatever data you want (a VLC stream of a 4k movie) with tunneling.

I do agree that new Linux users who have different needs from their computers might cause some incentive to change some of these 40 year old UX decisions. We don't really have a modern, capable remote desktop solution at least on par with RDP.

>character-only trash from 1960s

You take that back!

>Why a TUI is the best thing we pipe through ssh? Why I cannot watch a 4k movie in the terminal or browse the web using pinch to zoom?

The old magick speak of X forwarding. The newer wizards now use waypipe.

> Why ssh terminal has to look like character-only trash from 1960s?

We should re-implement it with Comic Sans and happy shiny buttons to click everywhere? Click here for "ls -alh" ?

No, but I wouldn't mind if keyboard worked properly.

Where keyboard no work?

because it is TEXT

you want your GUI then set up VNC

The problem with VNC is the same as the problem with IRC. The new user experience is trash. They're both on the level of protocols, like SMTP is, so you get variable support for user quality of life features and users bounce because those features aren't built into the protocol. For VNC, it's per window support and image compression format/acceleration. For IRC it's pre-join-history scrollback, and anything you need a moderation bot for. SMTP's problem is spam. (Doesn't matter if that's a problem with the protocol or the wider situation and should be managed at the application level, it sucks for users.

Because content is orthogonal to form. Development at its core is virtually pure content. The form, the fonts, the graphics, the "pixels". It's noise with regards to the task at hand. It's not useless, because surely we have eyes and need to witness text on the screen (for now), but it is orthogonal to the main axis of resistance we are trying to overcome (for which we get paid).

People that don't understand the separation between content and form cannot separate between data and rendering, between models and views. They stuff JS in CSS and CSS in databases.

In short, they make shitty architects and are to be shunned from programming important software in general. No offense.