Over the course of using only Go at work for the last year-ish, my opinion went from:
Go has some weird opinions and safety rails, but the advantages are still nice
to:
I love Go’s restrictiveness and can’t imagine any other way
Not sure if it’s stockholm syndrome by now but it’s definitely grown on me.
For example, I tried adapting some C++ code to Go last week, and the person was doing mystring[len(mystring)] and it worked with no out of bounds errors :(
From the onset I’ve been viewing Go as the better C I needed. It did take me time to get used to the fascist gofmt, though. Today I mostly have gripes with the standard library, debugging and trying to get away from thinking in the event loop model (that took me so much time to internalize). Still enjoying the language and the tools.
I think the fascism of gofmt is great. After using go for a while, I miss a similar tool for other languages. I get by with clang-format for C, but it requires quite a bit of configuration, and still doesn’t get some things right.
Over the course of using only Go at work for the last year-ish, my opinion went from:
to:
Not sure if it’s stockholm syndrome by now but it’s definitely grown on me.
For example, I tried adapting some C++ code to Go last week, and the person was doing
mystring[len(mystring)]and it worked with no out of bounds errors :(From the onset I’ve been viewing Go as the better C I needed. It did take me time to get used to the fascist gofmt, though. Today I mostly have gripes with the standard library, debugging and trying to get away from thinking in the event loop model (that took me so much time to internalize). Still enjoying the language and the tools.
The best thing about gofmt is that there is nothing you CAN configure. It’s the gofmt way or the highway.
I think the fascism of gofmt is great. After using go for a while, I miss a similar tool for other languages. I get by with
clang-formatfor C, but it requires quite a bit of configuration, and still doesn’t get some things right.