4 ms·
A few weeks ago. And I'm not really referring to its weird behavior. To use cabal, you have to write a cabal file to specify dependencies, build instructions,
by burntsushi 14y ago
A few weeks ago.
And I'm not really referring to its weird behavior. To use cabal, you have to write a cabal file to specify dependencies, build instructions, etc. With the `go` tool, no such meta data is required. Everything that is needed to build a package is inferred from the source by the `go` tool. This is what makes it less annoying than most other distribution tools.
Of course, most other distribution tools support a larger number of options, so perhaps its not a fair comparison. But that is irrelevant to typical workflow annoyances.
- Peaker 14y agoWell, how can it infer the dependency on particular versions? Or on particular implementations of some interface you're using?
- burntsushi 14y agoIt doesn't. Hence: > Of course, most other distribution tools support a larger number of options, so perhaps its not a fair comparison. But that is irrelevant to typical workflow annoyances. If you need to stick to a particular version of a software package, the common workflow involves using existing tools. (i.e., fork.)