News for hackers. Stuff that matters.
Re:Go 1.8 Release Candidate 1 is released by Merovius on Wednesday January 11, 2017 @12:09PM (#13375464)
> Another issue is when you try to use a fork of one of library.

A fork of a library is either identical to the original, or a new library. And you could argue (or rather: I do), that it is a good thing that you need to explicitly specify which one you intend to use.

Re:Go 1.8 Release Candidate 1 is released by takeda on Friday January 13, 2017 @01:09PM (#13393005)
So let say you use code with many dependencies, but you want to make a small change in one of the dependencies. In other languages you would then just compile and be done with it, but now with golang you now need to also modify potentially hundreds of places unless you resort to somehow cheat golang.

As I said, being opinionated is great if the opinion matches yours otherwise you might end up fighting it on every step.