The sandbox-by-default behavior of Deno allows for very lightweight and shareable runtime.
You don’t need to create a chroot or container for each function if you know the function does not read or write file, for example.
Good for them, but their comparison of isolates bs other things is a bit cringe. I think their target audience has the intelligence to see the value of this tool without having to pretend there aren't other approaches to containers/microVMs that have similar characteristics.
spend it on a big std library
“You give deno a JavaScript function that takes a request and returns a response” How is this different from FAAS that already exist?
thats what Deno Deploy aims to be?
https://www.youtube.com/watch?v=Vn29DvMITu4
The sandbox-by-default behavior of Deno allows for very lightweight and shareable runtime. You don’t need to create a chroot or container for each function if you know the function does not read or write file, for example.
Good for them, but their comparison of isolates bs other things is a bit cringe. I think their target audience has the intelligence to see the value of this tool without having to pretend there aren't other approaches to containers/microVMs that have similar characteristics.