3 ms·
At a quick look this means you'll need to use a special ssh client to use their framework? Terminals are decoupled from the actual application for a good reaso
by nottorp 6y ago
At a quick look this means you'll need to use a special ssh client to use their framework?
Terminals are decoupled from the actual application for a good reason...
- em-bee 6y agoyes, but that's exactly why we are stuck and can't evolve. if we want to get something better than current terminals, a new protocol and client are needed. take mosh for example. it uses a different protocol than ssh too, which adds some interesting features. and it replaces ssh (except for relying on ssh to make the initial authentication) there is no reason why another alternative to ssh could not be created. if it's good, it will catch on. just like mosh which is slowly growing, and also like ssh was in the very beginning when it slowly grew to replace telnet.
- nottorp 6y agoYeah but that thing seems to suffer from architecture astronautitis and a desire to take over every function just like systemd... While, you know, ssh carries your bits and the terminal displays said bits, just like it displayed the telnet bits before. Decoupled is good.
- em-bee 6y agofair point. actually, i think i may have misunderstood the problem. ssh can tunnel anything, so whatever new protocol is devised, it should actually work though ssh. also i am not disputing that a new system could not be decoupled. i am just concerned that it should not be required to work with ssh if that becomes a limiting factor. architecture astronautitis is certainly bad, but maybe it's possible to create an implementation with a limited subset of features that are actually practical.