poesie.nvim VS baby.nvim

If this is the case, I'm not sure a user should be using neovim, because they are likely to be unsatisfied generally with the customization experience which going forward will require more and more lua. I think efforts like https://github.com/phaazon/poesie.nvim may help address this by adding a declarative plugin configuration layer in something like json which could be "set" by a GUI. I've been talking to phaazon how to move that effort forward.

Just as a reminder, lspconfig is one "front matter" to the client, the built-in client is usable without it, but I think it's more helpful to think of it as an API. That means comments like "make it easier to use", "add autocompletion", "make it install servers automatically" is not a neovim/neovim issue and not what this thread is for discussing. I made a proof-of-concept of a meta-package that bundles everything together (yes, it's a joke, but it does actually work) that someone can run with.