corfu

This is a good point, but I do want to mention that I feel like in the past 5 years we've had lots of extremely popular packages that hook into Emacs internals instead of rolling out their own architecture. For example, corfu [0] versus company [1]. Company works with capf, but you can also write your own backends for it (specific to company). Corfu also works with capf, but all backends are capf functions instead of a corfu specific backend. Another good example is eglot [2] versus lsp-mode [3]. Eglot is actually packaged with Emacs now. There's also other stuff, like vertico [4] (and others that are recommended to download) versus helm/ivy. I also want to mention that packages that hook into Emacs more don't necessarily mean that they're better. From my POV it's more like you get a lot more things for free and the documentation you dive

TUIs in Prolog sounds fun. The great thing about TUIs is that a simple text component is a universal widget. If the user can display text and capture events they can implement any interface components they want in terms of that. That said, whatever the framework provides pushes users in a particular direction. The core of the things I'm thinking of (some links below) is providing easily accessible context for the user right at the point where they are working. This can be completions at the cursor, or a quick key to pop up a command palette. Fuzzy search is standard. Here are some examples: * Corfu: https://github.com/minad/corfu * Vertico: https://github.com/minad/vertico * which-key: https://github.com/justbur/emacs-which-key * LazyVim: https://www.lazyvim.org/ I've included links that have screenshots showing how they work. The list is