News for hackers. Stuff that matters.
Re:Go and Versioning: Minimal Version Selection by littlestymaar on Thursday February 22, 2018 @08:26AM (#16437353)
Everyone in a team should use the same conventions. The idea that everyone eveywhere on the world should use the same style has no practical interest : you don't get any productivity from it.

It's just a philosophical stance, and a rather totalitarian one IMHO.

Re:Go and Versioning: Minimal Version Selection by grey-area on Thursday February 22, 2018 @10:17AM (#16438081)
The idea that everyone eveywhere on the world should use the same style has no practical interest : you don't get any productivity from it.

I disagree on that - it makes it much easier to share code and to use code from other teams, and removes a whole area which people waste a lot of time on (bikeshedding formatting issues).

Re:Go and Versioning: Minimal Version Selection by littlestymaar on Friday February 23, 2018 @03:08AM (#16444917)
> and removes a whole area which people waste a lot of time on (bikeshedding formatting issues).

Interestingly enough, I've never seen people bikeshed about code formating in a project using a style formater even if it is configurable. But everytime Go is talked about here on HN, there are many people complaining about gofmt not being configurable …

Re:Go and Versioning: Minimal Version Selection by pcwalton on Thursday February 22, 2018 @01:52PM (#16440210)
But by not having a maximum line length, everyone gets to bikeshed where to insert line breaks. Thus gofmt isn't doing its job.

(Again, maybe line length doesn't matter much in Go, since lines generally don't get that long in Go, but for lots of other languages gofmt's choice would not be acceptable.)

Re:Go and Versioning: Minimal Version Selection by grey-area on Monday February 26, 2018 @08:02AM (#16464958)
FWIW, I haven't noticed this being a problem in Go code. Perhaps in other languages it's more important.