There is one aspect where Ed maybe has an actual advantage: It keeps you in write mode and discourages editing.

cat > $filename will do that, too, but with ed I can switch back to command mode, save what I’ve done so far, and then continue by returning to append mode.

Though I could probably do the same with cat >> $filename, but I’m afraid I’d forget that I need to type > twice to append and end up overwriting the file. :)

This is why I prefer writing drafts in a chat with myself. Also because of the enforced pacing: the rhythm of hitting Enter when a line is done, and the leaving it as it is.

or use ex, similar enough to ed, has the vi : commands, and vi is one command away

ex is not ed. i have often wished for ve instead of vi though

vi, vi, vi - the editor of the beast

vi, vi, vi - the one for you and me

+1

I’ll definitely look into that, thanks

my vim annoyance is that its non nvi

The purpose of the perl-in-chroot portion of the article was more like ‘hey, this is how you would do it if you wanted to’. As I mentioned in the article itself, I only host static content.

Hopefully it'l eventually support something like proxying to a second http daemon, so for Perl you could chroot perl + Starman, and have httpd proxy to it

https://wiki.archlinux.org/index.php/Systemd/Timers#As_a_cron_replacement if you’re ok with the creeping horror that is systemd