what do you think about temporarily add a fork of lsp-mode to emacs-ng(like use-package and straight) and provide an optional feature "lsp-mode"(or something else) so users can give it try(it works, kind of)
requests like hover and documentHighlight are working, but for other requests I get different errors like Input/output error or broken pipe(seems to differ with different servers)
I think it doesn't make much sense to merge it into lsp-mode if it's only half functional and crashes every 10 minutes...when we maintain a fork we could improve the lsp-mode integration while fixing issues in emacs-ng, would make things easier
sorry I didn't reply
@reggiemarr:bridge.monster I also didn't give up the project. You're very welcome to contribute to whatever features you are interested in. But we still lack the manpower to review pull requests properly. The project has a certain complexity with the features that are already implemented, making it even more difficult. webrender is the most complex feature so it's probably not the best place to start(especially when harryfei doesn't has the time to support you).
What I'm doing is try to improve popular emacs features and I hope at some point the changes convince more people to give the project a chance. The async facilities that were added by @DavidDeSimone provide lots of possibilities to improve the performance and I think that's the easiest way to show the value of the project.