Luca Casonato

> Also the nice thing about asserting is that you can still have cleanup code in a `try {} finally {}` block. You can do that with `return` too :)...

Please include your `node` code too.

@kitsonk Maybe - I have some stuff to do on Monday, but I'll try to investigate this on Tuesday.

@devalexqt So I can reproduce Deno being slower than Node here, but not catastrophically slower like your benchmark suggests. I measured 1GB uploads to the Node server at 1.24 secs,...

I'll try that, thanks. > 2x-3x slower that node, looks catastrophic in my eyes, something wrong in deno code under the hood. I agree it isn't great, but 5s is...

> Ideally we'd print a stack trace originating at the call site of Deno.exit() I think we should print no stack trace, rather just show the exit code in the...

How would this represent a nested namespace? Ie `Deno.errors.Interrupted`?

We should also consider direct HTML generation in Rust from the structured data. This should be a stretch goal for after we have this structured data though.

This is correct. From the users perspective they are importing default right?

This makes sense to me, especially now that we store origin data (`localStorage`) in DENO_DIR.