There are many ways to run code at startup. cronjobs and systemd are common ways to handle this. I have also had things start automatically with my desktop environment which comes later in the boot process.

You may be accustomed to the process, but fixing issues in the registry is not intuitive. It is simple enough if you find a guide that tells you exactly which item you need to work on and exactly what the default is and what you need to change it to, but what if the guide isn’t exactly what you want?

In the GNU/Linux ecosystem, nearly every program has a config file. Sometimes each line has detailed comments in plain text around it you what the option does with examples of what it could be. If the documentation doesn’t exist, you can dig deeper and see what that option does in the source which is usually documented as well. Programming experience is not required to search for text and read comments. Such documentation is not equivalent in Windows.

The ability to edit titles seems like an obvious feature that Reddit never added.

This is the first top-level comment that hints at the main criticism against systemd. systemd is increasingly difficult to replace as time goes on. I like and use systemd because it has a fast boot, but I wish the project was developed in a more modular way that had choice built-in. It is instead developed as the way that everyone should systemd instead of alternatives. This philosophy gets in the way of distributions that want to provide alternatives (Devuan, Gentoo, Parabola, etc.). Some of the sysadmins I work with closely use Devuan and follow development. I hear the patch set around bypassing systemd grows in size and complexity each year which is worrisome for choice.

Manjaro had a rough history of not taking security seriously. I hope they have improved, but the impression stuck.

They have done a few things right by making Arch more approachable when Arch was more of a RTFM type distribution. Now Arch is easier and even ships with an installer, but Manjaro’s installer is easy.

The end result is still that the user still needs to manage an Arch distro. I would recommend learning the Arch way from Arch instead of taking the easy road.

If you want an easy distro, rolling releases, and up-to-date packages, I would recommend Debian Did over Manjaro. If you want Arch, use Arch.

One time I was listening to headphones walking home from the train in the rain after work in a major US city. I had an uneasy feeling and spun around ending up walking backwards. I’m face to face with a stranger who is uncomfortably close to me matching pace. I awkwardly said, “Hi.” Then, we were both uncomfortable. Nothing happened. I took my headphones off and continued a few streets to my apartment. Maybe something would of happened had I not spun around.

argos-translate for offline machine language translation.

tmux & neovim for editing files and organizing the terminal displays.

asciinema for recording and playing back terminal sessions.