4 ms·
Article mentions that the compiled code will also run on Node.js, does it mean it will be possible to use all zillions of NPM modules from Go at some point in t
by exebook 8y ago
Article mentions that the compiled code will also run on Node.js, does it mean it will be possible to use all zillions of NPM modules from Go at some point in time?
- colonelxc 8y agoThus solving Go's dependency management problem once and for all.
- eikenberry 8y agoSolving it by giving it a worse one.
- MoOmer 8y agoThat is the joke.
- littlestymaar 8y agoWorse than pulling master on github, really ? Npm has issues, but it's still way better than the state of the art of dependency management in Go. Left-pad was bad but the problem was fixed on npm's side after a couple hours. Go's equivalent isn't fixable: https://mobile.twitter.com/davecheney/status/855049071307792384 https://mobile.twitter.com/davecheney/status/855049071307792...
- mappu 8y agoPulling master on github isn't the "state of the art" for Go (it's dep and vgo).
- littlestymaar 8y ago`dep` is pulling directly from github … And `vgo`, while promising, is still a protype not ready for production[0]. [0]: https://github.com/golang/go/wiki/vgo#current-state https://github.com/golang/go/wiki/vgo#current-state
- cdoxsey 8y agocommit your vendor folder
- tomatsu 8y agoIn Chrome and Node, Wasm code is executed by V8. V8 can be embedded in C/C++/Go/etc applications. That allows you to use JS for scripting. This is quite different from compiling to Wasm, though.