authcompanion VS rusty_v8

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.

I'm building Lagon, an open-source [1] runtime and platform that allows developers to run TypeScript and JavaScript serverless functions at the Edge, close to users. The runtime uses V8 Isolates and is written from scratch using Rust and rusty_v8 [2], Deno's Rust bindings for V8.

[1] https://github.com/lagonapp/lagon

[2] https://github.com/denoland/rusty_v8

Not to denigrate your work, it's good what you're working on... but I can create JS APIs in Rust with native V8 bindings, too: https://github.com/denoland/rusty_v8/blob/main/examples/proc...

For more futuristic stuff, check out Typescript native Deno and rustbased v8

No, that will be rusty_v8

V8 Rust Bindings Examples — Rusty V8 GitHub

Can Deno be embedded in a larger Rust application? I know I can embed v8 directly https://github.com/denoland/rusty_v8 but I wish I could use other parts of Deno.

In particular, I wish I could write a Tokio async program in Rust, and load plugins using deno, and have this work seamlessly

> git clone https://github.com/denoland/rusty_v8.git denoland/rusty_v8