I highly doubt this would be "the next node", if that is the intention. If you want to use Go, just use Go.
It doesn't make sense to create Show HN for any ol project.
Apologies if I screwed up. Definitely not trying to take credit for Ryan's work.
I was playing with v1 of this project (the non-TS one). Super excited to see progress on it. What are your plans?
Is it single threaded, non-blocking IO? Or will it more closely aligned with Go coroutines? i.e. do I have to deal with callbacks and/or async/await?
You're probably running untrusted JavaScript in your browser right now. The difference between the V8 in Node and the V8 in your browser is that one is heavily locked down and the other can do essentially whatever the OS lets it.
If you have untrusted code to run, you can eliminate a whole class of security concerns by just not having a way for the code to do those things (i.e., making syscalls it shouldn't, forking, reading and writing to the disk or network, etc.). Sure, resource use can be an issue, but that's a problem that's more easily solvable further up the stack with VMs or containers. Just putting an instance of Node running untrusted code in a VM doesn't solve much, since the mechanism whereby you give it input and collect output can be manipulated by the untrusted code itself.
By making the runtime secure, you get the security of the browser (i.e., being able to visit a website without having to wipe your machine), but designed to run in a server environment.
Everyone keeps saying this, let containers handle cpu/heap but I keep asking myself, is it really optimal?
If anything this is only partially true: "Package plugin implements loading and symbol resolution of Go plugins."
If I get it right, ts-node is just a transpiler, but deno runs "proper" ts?
I've done some concept/prototype for this but in the browser, and the main complaint is that it takes a few extra ms the first time you run the program. But as this is meant for servers and not impatient users, the extra startup time should not be a big issue.
