Caddy v0/1 was just built up naturally bit by bit, never had a proper design/structure around its config. Caddy v2 was a complete rewrite from the ground up, including thinking a lot more about config design, so it had to be a breaking change for the project's future to thrive.
Not directly related to the question. A few years ago, I read about that B-tree is also recommended for in-memory operations because the latency between CPU/memory is high now.
Agree, /var/log/messages is there for a long time, writing to log is never a problem. Digesting the log is the niche market and it is profitable enough that we have a lot of tools in this market (rotation, transmission, parsing, etc)
Yes, Alpine is a good choice for small servers. I run both FreeBSD and Alpine for my homelab. Alpine feels very close to FreeBSD style. I still prefer pf over ufw/awall.
I tried to install OpenBSD on three VM hosts, one Macbook Intel, one FreeBSD and one KVM. OpenBSD failed to install in all three environments. The latter two crashed just during the file system creation stage.
I picked up Emacs this summer (together with neovim). The motivation was simple, I was an early adopter of VSCode and SSH remote, but I noticed that sometimes, the session history (bash history, etc.) was not restored after network issue. I don't get along well with tmux thus I need a solution.
I found Emacsclient is a perfect match to my situation and I simply started from empty init.el. It was annoying in the first a few days to set up LSP, counsel, org-mode. But after about 3 days, everything became very natural and I have been using Emacs ever since. I made a lot of elisp in my init.el to set layout, do automatic actions, etc.
I am not a long time user yet so I can speak for the "learn" part: just use it and you will pick the skill up.
When I first read about RWKV on zhihu and the author said Bellard was working with him on RWKV. I am so glad ts_zip is out and bring a new application to RWKV.
