@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. ๐
@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. ๐
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.
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 @paul @sotolf @thedoctor
pico was my first unix editor. It took me 8 more years to finally learn vi properly, although I was only using Unix regularly for maybe two of those years.
Thank goodness for easily accessible Unix OSes these days! :D
(I mean, Linux, and a little later FreeBSD were available for all of those years, but not as well known, and hardware itself wasn't nearly as accessible as it is today (nor the OSes as capable to run on off-the-shelf hardware))
@paul @rl_dane @sotolf @thedoctor ugh, pico and its clone GNU nano are just eurgh. No.
I had mcedit and indeed mediรฆval versions of joe/jstar very eary on GNU/Linux.