authcompanion VS emacs-ng

What are your thoughts on something like this: https://github.com/authcompanion/authcompanion

I'm making a similar one here: https://github.com/authcompanion/authcompanion, if you wouldn't mind sharing your impressions of it.

Here's our token-based user management server using Deno if you'd like to see an example.

https://github.com/pmprosociety/authcompanion

AuthCompanion is a token-based authentication server (Deno) which helps developers build apps for the web, faster.

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