#KDE's #KRDC makes it stupid easy to set up a profile to use ssh tunnelling by default. That's really nice. Only downside is that it doesn't automatically re-connect when you resume from suspend.

@rl_dane but that's what autossh is for!

Do one thing and do it well - Unix πŸ‘

Do all the things! - KDE and Gnome and systemd too probably. πŸ‘Ž

@paul @rl_dane Is "provide a good UI for users to use their computer" not one thing?
@thedoctor @paul @rl_dane Well, I don't know if it is my personal deficiencies, but I find it easier to do it in text, it's clearer, easier to find, and I can do troubleshooting easier because I can see the logs when something didn't go the way I wanted them to.

@sotolf @thedoctor @paul

This is why I wish Jef Raskin had won at Apple, instead of Steve Jobs.

Steve gave us a user-friendly computer with limited utility.

Jef would've given us a slightly less user-friendly paradigm (text-based OS) that would have been much more empowering.

An entire generation raised on Jef's ideas would have been far more competent at using computers than the generation raised on the GUI.

@rl_dane @thedoctor @paul yeah I never grew up in the ui world, starting out with dos computers, uis is something that belong in programs and games to me, the os doesn't really need it, but of course that's my bias as someone that just works there.

@sotolf @thedoctor @paul

I actually wish CLI/TUI Unix programs would learn some lessons from the DOS programs of yore.

I find stuff like Lotus 1-2-3 way more intuitive than (neo)?vim.

Something that the DOS world successfully borrowed from the Macintosh world is a semi-standardized set of keybinds and interaction paradigms.

In the Unix world, you have vi-style, emacs-ish-style, and nearly every program requires memorizing custom keystrokes, unless the program itself is very customizable.

cc: @mirabilos

@rl_dane @paul @sotolf @thedoctor yes!

(Which is why I stick to Wordstar keybindings for the editor and "Emacs" for the shell, and stick with pine/alpine as MUA having learnt its bindings in the late 1990s (but I refuse to even consider pico))

@mirabilos @rl_dane @paul @thedoctor Yeah, for some reason being a vim user for over 15 years I still prefer emacs for the shell, I'm used to it, and it's the standard, I try to be as comfortable with vanilla tools as possible since I have to work on different servers all the time, and can't or won't bother with importing all my dotfiles everywhere and install tools that I'd rather use.

@sotolf @mirabilos @paul @thedoctor

Using HP-UX 20+ years ago forced me to love set -o vi, as emacs mode wasn't an option in that old version of ksh. ;)

I still use vi mode to this day. I barely know the emacs mode keybinds. XD

Also, that old ksh required you to use a double-escape-key-press to trigger completion, rather than tab. That was really annoying. XD

@rl_dane @sotolf @paul @thedoctor mksh worked on HP-UX 20+ years ago, FWIW

@mirabilos @sotolf @paul @thedoctor

Even if I had known of it at the time, I wouldn't have tried to install it on 100 servers. XD

Although, I must terrifyingly admit that I later developed a script that could touch all servers and run commands on them simultaneously... and I was an infosec guy.

Plumbers have the worst pipes. XD

@sotolf @thedoctor @rl_dane @paul I was never fond of scripting that, but I do find using clusterssh to do that interactively on a dozen or so servers at a time delightful. Allows you to react, or even just account for differences.

That’s why I also dislike ANSI-Bell that much.

@mirabilos @sotolf @thedoctor @paul

In this case, it was an abomination using ksh, expect, and a certain vendor's security product for privilege escalation. XD