Nvim. autopair.nvim let’s you autoclose “begin[]” macros. Luasnip let’s you create custom snippets for every macro you use. I also use Emmet LSP for inline svg.

Fortunately such “new choices” get abandoned very quickly. Making new solution instead of improving existing ones is counterproductive. Unless there is a large legacy codebase. Smart people have invented Unix principles to avoid that.

Not really. Best Foss projects do not always thrive. Git wasn’t really better than mercurial. But it had happened to be published earlier, so it got wider adoption.

If you will create “next gen” desktop, you will just solve some problems of already existing ones and create your own. Maturity of software is far more important, than uniqueness. GNOME didn’t evolve into its current state for no reason.

Kavita, same as Komga requires too much RAM.

Komga can track ebook reading progress, by converting them to images.

It doesn’t support OPDS-PSE, which is the most common way of tracking progress.

It actually has a ui. But it looks minimal enough. I’ll try it.

Gollum. Hit integration is required if you value wiki content.

ConnectBot is fine.

Why do we invent new DEs instead of making proper settings app in already existing ones?