This is neat, but (and I say this as a 14+ year diehard Emacs fan and average-skill elisp hacker) this seems like a classic example of things in Emacs world being overly complicated.<p>I almost didn't comment because I hate to take a cool thing the author did and turn it into a negative, but I've been thinking a lot about this complexity lately because of a recent foray back into the Vim world.<p>I've been moderately Vim proficient for most of my career, and decided to give things another try now that Neovim and Lua-based configuration is so popular. I was astounded by how simple and straightforward it was to get an LSP + Treesitter + DAP + Telescope, etc setup working, and with a clean and relatively compact amount of code.<p>It just felt so uncomplicated, and everything just worked. No using temporary bridge packages for treesitter modes, while still needing to copy over your mode hooks and set parent keymaps. Fuzzy completion that is consistent and doesn't depend on which company backend is in use. DAP mode layouts that consistently work as well as e.g. VS Code (I still cannot get Python's Rich library progress bars to show up in dap-mode output on emacs).<p>I still prefer Emacs, but am glad I went around the block with Neovim. It's inspired me to start a ground up rewrite of my Emacs configuration in the quest for simplicity, so maybe there's hope for my config yet.