emacs-ng VS tide

This is exactly what emacs-ng does?

https://emacs-ng.github.io/emacs-ng/

> This project should be considered an additive native layer over emacs, bringing features like Deno's Javascript and Async I/O environment, Mozilla's Webrender, and other features in development. emacs-ng's approach is to utilize multiple new development approaches and tools to bring Emacs to the next level. It is maintained by a team that loves Emacs and everything it stands for - being totally introspectable, with a fully customizable and free development environment. We want Emacs to be a editor 40+ years from now that has the flexibility and design to keep up with progressive technology.

I guess it uses webrender instead of electron?

Now I'm failing on this instead: https://github.com/emacs-ng/emacs-ng/issues/218

Presumably because of emacs-ng [1], from the page " additive native layer over emacs, bringing features like Deno's Javascript and Async I/O environment, Mozilla's Webrender,".

[1] https://github.com/emacs-ng/emacs-ng

How does it compare with Tide? https://github.com/ananthakumaran/tide

I got to try my hands on Typescript in Emacs using tide, and I loved the autocompletion enabled by type-inference. But even besides type-inference, there's even the autocompletion for previously defined local variables that exists in other language tools including anaconda for python, which I don't see in my setup of SLIME/emacs.

You should try tide for TypeScript projects.

off topic: I've found tide-mode[0] to be pretty good to use with typescript on Emacs

[0] https://github.com/ananthakumaran/tide

Is there a way to autogen doxygen doc for C/C++? At least templates with the parameters types and return type? I do this with tide in Emacs with Typescript for example and it's pretty useful.

Anyone got any experience with this package? I have got it running but the default key binding to jump to a definition is not working at all. Stated here (https://github.com/ananthakumaran/tide) M-. should work but that seems to be already bound to something else.

Then I started with TypeScript and I was both amazed and saddened by it. For regular TS files, .ts it was amazing. The spacemacs typescript-mode was even better than rjsx-mode, all the types are shown perfectly in the bottom bar, autocomplete, auto-import... Everything. And thanks to tide. The sad part is: there is no tsx-mode, to write our .tsx files, we have to use web-mode. Don't get me wrong, this is a great mode, but React + Typescript were not the goals back then.