Would be nice also to have the V8 implementation in Rust as well.
You mean JavaScript implementation in Rust. V8 is one of the many implementations that is written in C++.
A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
11–20 of 68 posts
Re: A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
#12As a long time Node.js developer I took a look at the project but it's still a really half-baked implementation of the security flags. You almost always end up flipping all security switches off because your application needs every feature (network, filesystem, etc).
No package signing, no flags per module, no syscall whitelisting, etc.
Re: A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
#13Watch 10 things I regret about node. js - https://youtu.be/M3BM9TB-8yA from the creator of both node and deno to undersatnd his motivations behind the deno project. A very intriguing talk.
> Access between V8 (unprivileged) and Rust (privileged) is only done via serialized messages defined in this flatbuffer. Expect to see this in "n things I regret about deno"
Can you explain why?
Re: A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
#14Re: A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
#15As a contributor to Deno, I am actually quite surprised that this got resurfaced on Hacker news after the hype June last year. That being said, I suggest checking out this video (recorded this April) for updated information about Deno, since things have changed quite a bit since the initial announcement: https://youtu.be/z6JRlx5NC9E (Edit: fixed link, posted the wrong one. Why would YouTube think I want to share ads.…
fyi the sound gets much better at the 3 minute mark
Re: A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
#16As a long time Node.js developer I took a look at the project but it's still a really half-baked implementation of the security flags. You almost always end up flipping all security switches off because your application needs every feature (network, filesystem, etc). No package signing, no flags per module, no syscall whitelisting, etc.
It's not even 1.0 yet.
Re: A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
#17Would be nice also to have the V8 implementation in Rust as well.
You can post your opinion here: https://github.com/ansuz/RIIR/issues/
Re: A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
#18What makes this different from something like https://github.com/Agoric/SES ?
It is being actively developed. Has a large pool of active contributors.
Re: A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
#19Would be nice also to have the V8 implementation in Rust as well.
Re: A Secure Runtime for JavaScript and TypeScript Built with V8, Rust, and Tokio
#20Watch 10 things I regret about node. js - https://youtu.be/M3BM9TB-8yA from the creator of both node and deno to undersatnd his motivations behind the deno project. A very intriguing talk.
It is very interesting although I didn't really understand the 'security' part. The motivation seems to be twofold - some bad things have happened because of compromised npm packages and v8 happens to have a robust sandbox. This sounds like a solution looking for a vaguely defined problem. The illustrative example he gives is 'malicious linter'. Is malicious linter that important a threat?