Benjamin Gruenbaum
Benjamin Gruenbaum
> Thinking about this for a minute, you actually can distinguish cancellations from other errors. This isn't something I'd recommend for general people to use (general users should just treat...
I am currently both sick and on bereavement leave so I can't leave a proper full response but: There are two major issues with this: - I think breaking the...
> > I think breaking the way everyone checks errors everywhere is a huge breaking change and I am ver hesitant for Node.js to do it and break all our...
What sort of guarantees do we get in terms of isolation? Do we have a proven (as in formally) sandbox that is unescapable except with side-channels? This enables some interesting...
> (@benjamingr I assume you closed the issue accidentally? I'm reopening this) Yes, sorry.
> However, since the code evaluated in the ShadowRealm is still sharing the heap with the code outside of the ShadowRealm. This means it is still vulnerable to Spectre, etc....
For what it's worth you can do `require(path)` instead of `JSON.parse(fs.readFileSync(path))` which would work since you can `require` JSON files.
Welcome @daeyeon !
> buffer.slice() is mutable copy, uint8array.slice() is immutable. This is very bad. Recently got hit with a bug report. I was checking for the input to be instanceof Uint8Array and...
What about the following suggestion: - Old modules that use `Buffer` will use `Buffer` (for example readable streams that build heavily on them). - New modules and APIs will prefer...