-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
Always interesting to see how other people use Neovim and what they think is important! I found myself nodding my head to some of these and being completely unconcerned about others. In particular, I think that omnicomplete and completion in general is at a really good point for upstreaming. The landscape of completion sources hasn't been changing too much over the past few years, the problem is well understood, and the desirability is high (nvim-cmp is the fifth most starred Neovim plugin of all time).
I would like to call out that "make compiler plugins async" sounds like a simple change, but quickly becomes quite complex. Let's say you do an async :make, now you have a background process. How do you cancel it? How do you view the output? Can you hide it and then come back to it? Can you run more than one at a time? Can you view all running tasks? If you want to have only very basic controls you could do what vim-dispatch is doing, but I personally don't think it's very good. I think any solution shy of VS Code style tasks control will be insufficient, but I think the appetite for adding something that complex to core Neovim is quite low. That said, this (and more) is something I really wanted, which is why I wrote overseer.nvim
Have a look at https://github.com/pr2502/ra-multiplex made by a friend of mine