3 ms·
All these "features" of Deno are super cool, but why reimplement a runtime from scratch :( Can we not benefit in Node from what I essentially see as "package.j
by sktrdie 6y ago
All these "features" of Deno are super cool, but why reimplement a runtime from scratch :(
Can we not benefit in Node from what I essentially see as "package.json not mandatory" - which I think is already achievable with ES Modules - and "better permissions model"?
Maybe this can be seen as the effort from several years ago where a project "io.js" branched out of Node as trying to implement certain things the community didn't like. Then after a few years they were implemented into Node and io.js "died off". Although io.js had always the intent of being compatible with Node, so that definitely changes things.
- petercooper 6y agoSome of what Deno does can be done in Node or people are trying to implement it (I've seen some proofs of concept around the way modules are included). However, it seems that being able to write the runtime in Rust has been a big deal here as it dramatically changes how the runtime is distributed and the developer experience of writing extensions for it versus Node.
- sktrdie 6y agoHow is choosing between Rust and C++ as the language in which the thing is written in, an important thing to the users who only care about the JS/TS interface?
- mst 6y agoBecause, in the long run, rust is a much better language for writing this in, and will enable faster addition of features for the JS/TS interface and more certainty that the security level stuff is actually secure.