News for hackers. Stuff that matters.
Re:Go and Assembly by burntsushi on Thursday February 07, 2013 @08:05PM (#5185636)
> all of his bullets apply to GHC Haskell too

No chance. Using the `go` tool to install packages is at least an order of magnitude less annoying than using `cabal`.

Re:Go and Assembly by Peaker on Friday February 08, 2013 @04:33AM (#5187036)
When did you last use `cabal`?

Cabal works much better now, and most of the problems were due to over-conservative version ranges combined with an over-eager reinstallation policy that overwrote packages in a breaking way. That was fixed about 6 months ago, IIRC.

Re:Go and Assembly by burntsushi on Friday February 08, 2013 @06:34PM (#5190792)
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.

Re:Go and Assembly by Peaker on Saturday February 09, 2013 @05:40PM (#5194381)
Well, how can it infer the dependency on particular versions? Or on particular implementations of some interface you're using?
Re:Go and Assembly by burntsushi on Monday February 11, 2013 @04:32PM (#5203419)
It 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.)