deno-feedly VS emacs-ng

At the beginning of 2021, I want to challenge myself for more. It goes back to Deno, the fantastic web tech I loved with. Maybe collecting good articles on the web about Deno, just like my @ningowood/pen-source-magazine repo does, is a good way to start as well. So I brought the @hylerrix/deno-feedly repo into the Github world. Deno Feedly is designed for collecting and sharing news, articles, and more about Deno biweekly.

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