deno-tutorial VS emacs-ng

So I began my Deno adventure from that time. It seems that writing is something I'm better at. I started writing the most basic article about Deno and make some authorized translations into the Chinese Deno community. @hylerrix/deno-tutorial and a@hylerrix/awesome-deno-cn condensed all my early understanding of Deno. Meanwhile, in the whole of 2020, I started to write @ningowood/open-source-magazine in the Chinese community to know the philosophy of Open Source deeper by collecting and sharing news and articles monthly.

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