Really love these videos, they cover a broad range of practical stuff which just doesn't get covered elsewhere. Everyone should be integration testing their handlers, but I suspect most don't, even though the go http packages make it pretty easy.
Go is not an object-oriented language. ...It’s better to compose than inherit
This depends of course on your definition of Object Oriented, but I think it captures an important truth - Go is in many ways a rejection of modern OO programming, with all the ceremony and hierarchy that it involves, so though this idea is contentious, Go has dumped all of that in favour of composition. Nowadays when people talk about OOP, they really mean objects and inheritance.
Channels and goroutines are powerful way to solve problems involving concurrency
While I think channels are nice, they're also often overused by newcomers to the language.
There is nothing exceptional in exceptions
I do love this about go. Just wish they had completely left out panic, and perhaps had some sugar to make it slightly less painful to return an error (go is becoming infamouse for if err != nil which is a shame).
This does seem a little biased because the author is not writing server software, which is really the intended use of context. It does feel like cancellation is something that would be better built into goroutines though, rather than tacked on to every api.
Context may still be required in web apps though in order to thread request specific data through various levels of handlers/middleware.
smith is a simple command line utility for building microcontainers from rpm packages or oci images.
So this lets you build a container from a simple rpm package, and then deploy it using docker instead of the rpm? How do you get updates for the package later though?
Really nice to see this talk, and that the Go team are considering how best to introduce breaking changes, and also consulting with users of Go about what they'd like to see change and what problems they've encountered. One of the things I love about Go is how stable it is (which is probably a lot of hard work behind the scenes). It's boring, as I think Brad said in some talk, which is exactly what you want in a language (as opposed to libraries or apps, which can be a bit more adventurous).
It does seem Russ is trying to solicit problems rather than proposed solutions at this stage - always the hardest part of
I'm a little mystified as to why Generics are so contentious and excite the madding crowd so much over at reddit or HN on this topic. At the moment it might be partly that people have decided somehow the Go developers are hostile to generics rather than simply cautious about them (I think it's the latter). The built in functions acting on containers do feel like a bit of an ugly special case - just enough generic functions to get the job done I imagine was the thinking when they were put in, but why not let end users create generic functions? Nowadays this is expected, and in most languages (not C++) works quite well if used sparingly. I wonder if their hesitation is partly what if it is not used sparingly?
Things I'd like to see addressed:
Errors - would be nice to see better error types (encapsulating possible error and value), and neater returns (get rid of if err == nil {return nil,nil,nil,err})
Nil - wish they hadn't put it in, too late now though I suppose
Maybe get rid of the distinction between []byte and string
Containers - would be nice to see some facility for making better
containers which can act on many types, mapping a slice of type [] - sounds like they are considering
some form of generics to handle this.
Cleaner stdlib - again lots of things that could be tidied and then fixed in user code with gofix.
Russ on Generics from the reddit thread on this story:
Re generics: A few people have misinterpreted the part of my talk mentioning generics as saying I don't know any possible use cases for generics, sometimes followed up by talking about how important type-safe containers are. Obviously I know about type-safe containers.
The point in that paragraph, which was brief due to time reasons, was that if you don't have specific use cases in front of you, you can't tell whether the design covers them. Even "type-safe containers" is not very specific. If all we need is type-safe map/set/etc then a very basic polymorphism is OK and we can skip generic methods.
Mostly though I'd like my Go 1 code to just run with Go 2, without a massive painful migration for all those big projects and libraries that are already written in Go 1. Sounds great that they're considering backporting any changes they can, which is great.
This is fun to play around with, given the very fast compile times of go though I haven't found it a huge problem to just write the code I want then iterate by running it quickly all at once - having to import a lirbary in order to get an interactive repl and change the code on the fly seems a little gross, though it is a really fun interesting hack.
I really like context, it solves real problems, hope they don't get rid of it.
Really love these videos, they cover a broad range of practical stuff which just doesn't get covered elsewhere. Everyone should be integration testing their handlers, but I suspect most don't, even though the go http packages make it pretty easy.
While I think channels are nice, they're also often overused by newcomers to the language.
I do love this about go. Just wish they had completely left out panic, and perhaps had some sugar to make it slightly less painful to return an error (go is becoming infamouse for if err != nil which is a shame).
This does seem a little biased because the author is not writing server software, which is really the intended use of context. It does feel like cancellation is something that would be better built into goroutines though, rather than tacked on to every api.
Context may still be required in web apps though in order to thread request specific data through various levels of handlers/middleware.
Great work on liveblogging, I'm definitely feeling some fomo from not being there and seeing the twitter feeds.
It does seem Russ is trying to solicit problems rather than proposed solutions at this stage - always the hardest part of
I'm a little mystified as to why Generics are so contentious and excite the madding crowd so much over at reddit or HN on this topic. At the moment it might be partly that people have decided somehow the Go developers are hostile to generics rather than simply cautious about them (I think it's the latter). The built in functions acting on containers do feel like a bit of an ugly special case - just enough generic functions to get the job done I imagine was the thinking when they were put in, but why not let end users create generic functions? Nowadays this is expected, and in most languages (not C++) works quite well if used sparingly. I wonder if their hesitation is partly what if it is not used sparingly?
Things I'd like to see addressed:
Russ on Generics from the reddit thread on this story:
Mostly though I'd like my Go 1 code to just run with Go 2, without a massive painful migration for all those big projects and libraries that are already written in Go 1. Sounds great that they're considering backporting any changes they can, which is great.This is fun to play around with, given the very fast compile times of go though I haven't found it a huge problem to just write the code I want then iterate by running it quickly all at once - having to import a lirbary in order to get an interactive repl and change the code on the fly seems a little gross, though it is a really fun interesting hack.