5 ms·

I think this very specific details is what summarize to me the pain of using go. Everything is a "convention" but nothing is enforced in a way that would make

by h1fra 4y ago

I think this very specific details is what summarize to me the pain of using go. Everything is a "convention" but nothing is enforced in a way that would make it easy for developer. There is actually nothing preventing you to not write doc comments like that, nothing to enforce err check, to put interface{} everywhere, to assign nil to a pointer, etc... By design the language is actually super loose and it heavily contradicts the goal of the language itself. When they say it was for junior/quick onboarding I have nervous laughs, I never saw that much coding mistakes happening to senior devs than in a Go codebase. You only follow standards if you use golangci which is not even an official tool.

rob74 4y ago
If you think Go is bad, I hope you never have to work on a project with eslint - its default configuration is pure OCD (complains about max line lengths, spacing before/after operators, using "++" etc. etc.), and 90% of the things I find most annoying could be fixed by using gofmt in Go - except of course there is no built-in formatting tool for the JS ecosystem...
- mwcampbell 4y ago
  > except of course there is no built-in formatting tool for the JS ecosystem What about prettier? Sure, it's not "built-in", but it's still easy enough to use and enforce within a given project.
  - deleted 4y ago
    [deleted]