2 ms·
I count one dependency, on wazero itself. Also, the Go SDK. There is also the OS and the hardware. I think what they mean to say is that their module has no a
by skybrian 3y ago
I count one dependency, on wazero itself.
Also, the Go SDK. There is also the OS and the hardware.
I think what they mean to say is that their module has no additional dependencies on other modules. But, how much should users care? Go is pretty good at managing dependencies and they’re okay within reason.
It seems like an odd way to name your module? I guess it shows commitment. But if they later decide on adding a dependency, they could rename it.
- evacchi 3y agoThe "zero-dependency" in this context really means zero dependencies from Cgo :) see https://news.ycombinator.com/item?id=36552401 https://news.ycombinator.com/item?id=36552401
- skybrian 3y ago“Pure Go” seems like a fairly common way to talk about that. But I suppose generated Go code should be okay? Definitions are hard.
- evacchi 3y agoit's a bit more nuanced than that, we are also trying to actually limit third-party dependencies, you can read more about it here https://github.com/tetratelabs/wazero/blob/main/RATIONALE.md#zero-dependencies https://github.com/tetratelabs/wazero/blob/main/RATIONALE.md...
- skybrian 3y agoThat’s a pretty deep rabbit-hole. Thanks!
- circuit10 3y agoThere’s a section on the site for this: “Why zero? By avoiding CGO, wazero avoids prerequisites such as shared libraries or libc, and lets you keep features like cross compilation. Being pure Go, wazero adds only a small amount of size to your binary. Meanwhile, wazero’s API gives features you expect in Go, such as safe concurrency and context propagation.” Though that seems to be more about specifically C dependencies