undefined | Better HN

0 pointselectroly7y ago0 comments

Native code has two benefits over JavaScript: it's faster, and it can call the OS. WASM is faster, but it can't call the OS. It cannot replace all uses of native modules.

0 comments

zeroname7y ago

Calling the OS doesn't require native modules, it should be supported via a native cffi in node, like in Python.

electrolyOP7y ago

Are you describing something you wish that node had, or something that actually exists? As far as I'm aware, native modules are the FFI for node, and that every package that involves presenting an FFI to the developer is using a native module to do it.

zeroname7y ago

Node doesn't have it natively like Python does, but it exists:

https://github.com/node-ffi/node-ffi

1 more reply

mixedCase7y ago

Wasm on the browser can't call the OS, but I don't assume that to be the case on Node, just like it isn't for JS.

mhenr187y ago

JS (and eventually wasm) calls the OS via requiring native modules, which is why we're concerned about keeping them around.

j / k navigate · click thread line to collapse

0 comments

zeroname7y ago

Calling the OS doesn't require native modules, it should be supported via a native cffi in node, like in Python.

electrolyOP7y ago

zeroname7y ago

Node doesn't have it natively like Python does, but it exists:

https://github.com/node-ffi/node-ffi

1 more reply

mixedCase7y ago

Wasm on the browser can't call the OS, but I don't assume that to be the case on Node, just like it isn't for JS.

mhenr187y ago

JS (and eventually wasm) calls the OS via requiring native modules, which is why we're concerned about keeping them around.

j / k navigate · click thread line to collapse