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.
Professor Bao of the OpenXiangShan team is known for his outspokenness, particularly in advocating for the academic model of the RISELab at UC Berkeley, which he often refers to as "Open Source Heavy Industry". As a result, he is a strong proponent of the OpenXiangShan project, as he firmly believes that it is the ideal means of producing high-quality research.
Providing legal protection for lawsuits can be a lucrative business. However, I'm not aware of any BSD-based companies that have capitalized on this opportunity. Are there any untold stories?
IMHO, SO is tech-stack centric, which worked perfectly in old days. Questions are grouped by Java, Web, .NET, shell/system admin, etc. We got most of answers to general questions for each tech stack in SO. But nowadays, with the rise of open source projects, the knowledge of each project stays with the GitHub issues. This is naturally shaped by the domain knowledge of each project. I would say SO may not see any rapid growth anymore, Github will.
In early attempts of removing GIL, atomic reference counting slows down performance by 60%. In comparison, tracing garbage collector can defer/coalesce reference counting. You can read more in [2] section 2.1, and this paper introduced a new referencing counting method.
Also, firecracker did not merge virtio-fs [1]. So I guess it is a scope and priority decision:
> To not trade off our core use case simplifying assumptions, we'll need something like a way to build different Firecracker "specialized variants" or alternatively a plugin system. This is something worth discussing for 2021. Again this is not a guarantee, but virtio-fs could fit in such a scheme, especially if it's a rust-vmm crate we can easily import over.
Leadership or steering committee is a key factor for open source projects operated by companies. A closed pull request with comment "We won't accept the pull request because ..." should not be on the trajectory of an infrastructure project, which is to be/being widely used by any giant vendor.
So RocksDB came from LevelDB and here we go again.