> it may use a custom API that does not line up with the spec
Not sure about that, but it's been working brilliantly for me so far.
> API compatible with browser RTCPeerConnection
Fair enough, though I'd be curious what you'd be doing with Node not in a browser that requires this...
> Also, when you say native, I guess you mean just in Node, right?
Yeah, sorry I guess "native" was the wrong word there.
> C++ or wasm binaries are going to be faster
True, but if you are trying to distribute your NPM package to lots of users, and it requires platform specific binaries or, God help us, node-gyp, you're in for a lot of GitHub issues :)
Not sure about that, but it's been working brilliantly for me so far.
> API compatible with browser RTCPeerConnection
Fair enough, though I'd be curious what you'd be doing with Node not in a browser that requires this...
> Also, when you say native, I guess you mean just in Node, right?
Yeah, sorry I guess "native" was the wrong word there.
> C++ or wasm binaries are going to be faster
True, but if you are trying to distribute your NPM package to lots of users, and it requires platform specific binaries or, God help us, node-gyp, you're in for a lot of GitHub issues :)