ガブリエル

This has been a thing since Linux kernel version 5.0.

How come it doesn’t work? Which compositor are you using?

0.x versions allow for breaking changes to be made to configuration (and whatnot), which allows stabilization for 1.x versions (which OTOH shouldn’t allow breaking changes without a major bump).

I’m currently using Gentoo. That means I should also grow my own food…

To complement your answer, usually people want tree-sitter not only for smart selections, but because of syntax highlighting.

Kakoune has the best of both worlds: https://github.com/kak-lsp/kak-lsp supports semantic highlights from LSP servers, but we also have projects like https://github.com/phaazon/kak-tree-sitter in case you want highlighting from tree-sitter.

Well, that’s Fedora, my friend. On Gentoo it’s still the same.

Short answer: if you’re asking this, then it’s not worth it.

Long answer: Ditching systemd in favor of something else is usually an act of experimentation. Folks that do it usually have had a negative experience with systemd, be it in its usage or from a problem they had that prevented them to boot their computers due to the tightly-coupled relationship between mainstream distros and systemd.

Also, preference is involved here, so you might prefer to assemble your system with independent pieces instead of a full-blown suite like systemd’s. You might also not like systemd’s UX so, as a user, you end up wanting to try something else.

Ok but nowadays there are alternatives to systemd (OpenRC, runit). Not necessarily better, just alternatives. No SysV init involved.

I’m not. But I installed Gentoo on a x86 tablet, it was fun.

I like compiling Gentoo on tablets