[TheAceOfHearts]

One of the nice things about JS versions of stuff is being able to run it everywhere. With that being said, I'd be skeptical of using this since it doesn't appear to have any tests at all. How do we know it's actually compatible with libsignal?

[mschulze]

> One of the nice things about JS versions of stuff is being able to run it everywhere.

To my knowledge node does not run on SPARC processors (because V8 doesn't).

[Zoon]

I remember reading that they made it engine-agnostic a while ago.

[kristiandupont]

That doesn't (yet) work with native libraries though.

[jdc0589]

yep. example: https://github.com/nodejs/node-chakracore

[egeozcan]

This has a native part written in c and only runs on node.js v8 and up, according to the package.json.

[qznc]

So it is "bindings", but not a "port"?

[tooker]

The C components are just a few emscripten compiled curve25519-donna and ed25519 functions for elliptic curve routines. It comes directly from the web library without any alteration. Honestly I was surprised at how well it works and the performance isn't too shabby. I did several investigations of replacing it with libsodium and others but the the emscripten builds have been pretty reliable for us..

[jszymborski]

The original version is written in Java, which sorta invented "run-it-everywhere"

[dabockster]

Meh, I personally prefer "complie-it-everywhere" since you gain all the speed benefits of running it native.

[justinjlynn]

Well, to be fair, with Java you are compiling bytecode everywhere before and while you run. So, you're not wrong.

[dabockster]

Still in the JVM, though. I was thinking more bare metal.