Evidently I’m similarly old, but a lot of the TUI apps replacing old standards look better.

Whatever wezterm uses to render ligatures has made editing quite pleasant, it doesn’t eat random control characters either which I found insufferable in a few that ship with DEs. Its still miles better than the cart, YMMV depending on what you use it for.

Depends on what you’re beginning.

The risk of forgetting some critical part of the install is mostly mitigated by arch-install. Arch is one of the easiest to “learn the ecosystem” since all packages are delivered to you as the author wrote them, so your first time through is a chore, but afterwards you can pretty easily replicate what you land on.

There’s a lot more decisions made for you in other distros, ultimately I found it frustrating to work backwards trying to understand what those were the more polished they came.

It is however; the absolute last place I’d point someone who didn’t want to or did not have the time, no matter how good the arch wiki is: it doesn’t read itself.

I did this for awhile…

https://github.com/systemd-cron/systemd-cron-next

If I remember whatever chef script I was blowing out mucked up something enough I ended up ditching it and manually rebuilding the timers as sysd units.

Even as someone who likes systemd since trying to teach init is pretty uniquely awful, I still have a load of one a year cron jobs I just use a BSD box for.