3 ms·
I am inclined to say that a low pace of change isn't necessarily a problem for something that at its core emulates 70s hardware. It can easily become a problem
by boomlinde 2y ago
I am inclined to say that a low pace of change isn't necessarily a problem for something that at its core emulates 70s hardware.
It can easily become a problem if you don't leave it at that and add everything and the kitchen sink to it. Not having used the feature I have a hard time imagining why a terminal emulator should have SSH integration to begin with.
- saagarjha 2y agoHardware in the 70s was full of security issues. Designing a secure terminal emulator is actually quite difficult.
- boomlinde 2y ago> Hardware in the 70s was full of security issues. It's however clearly not in the "70s hardware portion" of iTerm that this issue arises. Also not in the features we've come to expect of the most bare bones terminal emulators since, like Unicode support, scrollback buffers and font rendering, or even the somewhat gratuitous features like escape sequences for RGB colors, setting the window title or sixel rendering. This is very clearly one of the kitchen sink features, and playing the devil's advocate I should say that it reflects poorly on the kitchen sink design ethos.
- kmacdough 2y agoThe comment puts the slow pace of change as an advantage. Pretty standard security principle. Ssh integration brings lots of other "local" iterm features based on command history, etc. to the ssh environment. If you do lots of ssh work and use a lot of relevant iterm features then it's nice. Otherwise not. Obviously, these features can be recreated with traditional tools. But these tools take time and experience to setup, and aren't naturally intuitive, despite the insistence of emacs elitists. For those who don't want to invest significant effort learning tmux, it's really nice to just check/uncheck a few boxes.