Show HN: Node.js port of WhisperSystem's libsignal
1–10 of 17 posts
Re: Show HN: Node.js port of WhisperSystem's libsignal
#2One 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?
Re: Show HN: Node.js port of WhisperSystem's libsignal
#3One 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?
This has a native part written in c and only runs on node.js v8 and up, according to the package.json.
Re: Show HN: Node.js port of WhisperSystem's libsignal
#4One 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?
This has a native part written in c and only runs on node.js v8 and up, according to the package.json.
So it is "bindings", but not a "port"?
Re: Show HN: Node.js port of WhisperSystem's libsignal
#5What disturbs me about this port is that they did not use Typescript. I would have expected that they would use a strongly typesafe language in the ideal case.
Re: Show HN: Node.js port of WhisperSystem's libsignal
#6One 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?
> 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).
Re: Show HN: Node.js port of WhisperSystem's libsignal
#7One 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?
> 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).
I remember reading that they made it engine-agnostic a while ago.
Re: Show HN: Node.js port of WhisperSystem's libsignal
#8Earlier quoted context omitted.
> 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).
I remember reading that they made it engine-agnostic a while ago.
yep. example: https://github.com/nodejs/node-chakracore
Re: Show HN: Node.js port of WhisperSystem's libsignal
#9Earlier quoted context omitted.
> 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).
I remember reading that they made it engine-agnostic a while ago.
That doesn't (yet) work with native libraries though.
Re: Show HN: Node.js port of WhisperSystem's libsignal
#10What disturbs me about this port is that they did not use Typescript. I would have expected that they would use a strongly typesafe language in the ideal case.
Many checks still need to be done in runtime. Bindings to C code can cause the program to exit if you pass incorrect input.