The State of Go
talks.golang.org
The State of Go
1–10 of 402 posts
Re: The State of Go
#2Awful to try to read on mobile. Regular page anywhere?
Re: The State of Go
#3Awful to try to read on mobile. Regular page anywhere?
I agree ... Even on an iPad, impossible to navigate correctly, slides stopped in between when you swipe
Re: The State of Go
#4https://tip.golang.org/pkg/sort/#Slice
ouch compile time type safety... even Go maintainers have abandoned it. Go pundits can't expect developers not to do the same thing in their own codebase at that point.
Can't wait for aliases though.
Re: The State of Go
#5I'm at FOSDEM where this talk was just given. Francesc was hilarious.
Re: The State of Go
#6The best summary I read recently is that go isn't a bad language, nor is it a particularly good one. What fascinates me is the way the Golang community have concretised that essential middle-of-the-roadness as the language's prime virtue. That, of course, has long been Java's prime virtue as well. (see Blub Paradox)
By putting "we're okay with being okay" as your Big Thing you're clearly pitching for that vast bulk of mid-quality developers that make up the huge middle chunk of corporate devs, the space where Java reigns supreme.
Re: The State of Go
#7My impression is that Go is a language that was cobbled together to simplify the coding of some specific applications, such as simple servers. It lacks any kind of purity, is not the best choice for any specific task, but is just good enough for some (many?) tasks. And poor type safety!
Frankly, I can't help being disappointed by how bland this language is, and I have zero interest in using it. Maybe because I like coding, and the IMHO using Go or Java would totally kill the fun of it.
Re: The State of Go
#8My impression is that Go is a language that was cobbled together to simplify the coding of some specific applications, such as simple servers. It lacks any kind of purity, is not the best choice for any specific task, but is just good enough for some (many?) tasks. And poor type safety! Frankly, I can't help being disappointed by how bland this language is, and I have zero interest in using it. Maybe because I like c…
But if you like typing `if err != nil` it's actually the most fun language.
Re: The State of Go
#9https://tip.golang.org/pkg/sort/#Slice ouch compile time type safety... even Go maintainers have abandoned it. Go pundits can't expect developers not to do the same thing in their own codebase at that point. Can't wait for aliases though.
The ability to provide inline comparison function for Sort() is welcome. It's one of those infrequently needed language niceties that have (at least for me) made perl and python so slick to use.
Sorting arrays of objects or small hashes, based on arbitrary properties/keys, is quite useful.
Re: The State of Go
#10The best summary I read recently is that go isn't a bad language, nor is it a particularly good one. What fascinates me is the way the Golang community have concretised that essential middle-of-the-roadness as the language's prime virtue. That, of course, has long been Java's prime virtue as well. (see Blub Paradox) By putting "we're okay with being okay" as your Big Thing you're clearly pitching for that vast bulk o…
Do you have an example of the community celebrating mediocrity?
My impression is of a community willing to go without some features, in order to preserve those it values. Namely simplicity, explicitness, terseness, and consistency.