Paul Phillips here. I searched my tweet archive for my tweets about Go. Draw your own conclusions.
- Kill me before I look at go.
- Nobody shot me first so I looked at go. Sigh. After maybe an hour of go I was ahead of where I was after a week with rust.
- The first audible WTF with go: cuddled else is mandatory. Parse error otherwise.
- go is a terrible, terrible language, yet still a major productivity boost. Amdahl's law in another context.
- You often see languages which are fighting the last war. Go is fighting the War of 1812.
- If someone had made up Go within a work of fiction, they'd have been laughed out of the room.
- I had thought Blub was a rhetorical device, but Go is more Blub than Blub.
- reduce: what you will do with your expectations after you start with Go
- Did they miss any chance to introduce an ad hoc inadequate non-solution? Tool directives in comments! What could go wrong!
- Comical levels of confirmation bias in proglangs. Guy doesn't get it, poor impl, isn't useful, "see?" Examples: scala, python, go.
- Some specifics are enumerations in scala, closures in python, and anything devised since 1980 in go.
- Go: compiler directives in comments is "an elegant design". https://t.co/DjCO1UxgC2 http://t.co/BR3kFxRZvc
- Rust and Scala drown you in complexity. Go drowns you in simplicity.
- This comment sums up Go pretty well. https://t.co/Td9Q3wOW43
- go logging package lets you set the global Writer, but not query it. So you can't save/restore it. Nice job.
- This year's gold medalists in type safety's missing-the-point olympics: Go! https://t.co/ktrlBUEwP9
- Turns out Go is the result of a bar bet between Rob Pike and Robert Heinlein. Everybody lost.
- It’s incredible how far Go has lowered my estimation of the vaunted Google engineer. What an institutional failure.
- Go is what you might come up with if your definition of programming was “shuffling electrons”.
- A Go discussion thread is “how to build a space station with crayons” up to homotopy.
- A supposed selling point of Go is that you can learn it in a day. Think of what that tells you about what it can do.
- The existence of Go leads me to realize the infamous Google technical interview is designed to weed out out-of-the-box thinking.
- I added a second file to https://t.co/ktrlBUEwP9 further explaining how go's casting requirements are broken by design.
- But little did I know, I’m just a “lesser” programmer because I enjoy Go’s simplicity" says a commenter. Well, yeah.
- The Go string type can't be passed as a fmt.Stringer. You apparently have to accept interface{} and type match. Amazing.
- An example of go upside: "go get ...gocov" and code coverage instantly worked. In scala it has always been painful/fragile at best.
- Any go code which has error in parameter position which tests err against nil will silently miss a bunch of errors.
- Hostility to abstraction: the Go story
- Sad that google waited this long to put a deep mind on go.
- Kill me before I look at go.
- Nobody shot me first so I looked at go. Sigh. After maybe an hour of go I was ahead of where I was after a week with rust.
- The first audible WTF with go: cuddled else is mandatory. Parse error otherwise.
- go is a terrible, terrible language, yet still a major productivity boost. Amdahl's law in another context.
- You often see languages which are fighting the last war. Go is fighting the War of 1812.
- If someone had made up Go within a work of fiction, they'd have been laughed out of the room.
- I had thought Blub was a rhetorical device, but Go is more Blub than Blub.
- reduce: what you will do with your expectations after you start with Go
- Did they miss any chance to introduce an ad hoc inadequate non-solution? Tool directives in comments! What could go wrong!
- Comical levels of confirmation bias in proglangs. Guy doesn't get it, poor impl, isn't useful, "see?" Examples: scala, python, go.
- Some specifics are enumerations in scala, closures in python, and anything devised since 1980 in go.
- Go: compiler directives in comments is "an elegant design". https://t.co/DjCO1UxgC2 http://t.co/BR3kFxRZvc
- Rust and Scala drown you in complexity. Go drowns you in simplicity.
- This comment sums up Go pretty well. https://t.co/Td9Q3wOW43
- go logging package lets you set the global Writer, but not query it. So you can't save/restore it. Nice job.
- This year's gold medalists in type safety's missing-the-point olympics: Go! https://t.co/ktrlBUEwP9
- Turns out Go is the result of a bar bet between Rob Pike and Robert Heinlein. Everybody lost.
- It’s incredible how far Go has lowered my estimation of the vaunted Google engineer. What an institutional failure.
- Go is what you might come up with if your definition of programming was “shuffling electrons”.
- A Go discussion thread is “how to build a space station with crayons” up to homotopy.
- A supposed selling point of Go is that you can learn it in a day. Think of what that tells you about what it can do.
- The existence of Go leads me to realize the infamous Google technical interview is designed to weed out out-of-the-box thinking.
- I added a second file to https://t.co/ktrlBUEwP9 further explaining how go's casting requirements are broken by design.
- But little did I know, I’m just a “lesser” programmer because I enjoy Go’s simplicity" says a commenter. Well, yeah.
- The Go string type can't be passed as a fmt.Stringer. You apparently have to accept interface{} and type match. Amazing.
- An example of go upside: "go get ...gocov" and code coverage instantly worked. In scala it has always been painful/fragile at best.
- Any go code which has error in parameter position which tests err against nil will silently miss a bunch of errors.
- Hostility to abstraction: the Go story
- Sad that google waited this long to put a deep mind on go.