|
|
|
|
|
|
by mk89
1297 days ago
|
|
|
I think SWIG had a different purpose. The author here generates and embeds WebAssembly in Go, to avoid building the same lib for multiple platforms (+ the bindings to call the low level c code). Maybe the tool wasn't good enough? Right now this is just WebAssembly which is proven to work on multiple platforms. If the API is clear and documented, I don't see why this would be an issue, except for the fact it might be a little bit clunky. It's not the first solution I would come up with, but the question would be: why not? Just because we're used to older and more traditional patterns, why not just to embed webassembly for low level stuff in your code? |
|
|