nathany's comments

Get Programming with Go is a beginner's guide to the Go programming language containing 32 quick lessons with plenty of fun exercises and silly gopher illustrations.

It's now available in print, and my publisher has made it the deal of the day today (September 19th, 2018). Get half off the ebook and print versions, with international shipping available.

Deal of the Day: https://yng.mn/dotd

You can read through this thread to see what people want to work on for Go 1.8.

https://groups.google.com/forum/#!topic/golang-dev/098vr4999...

Yup, and you can always rename vendor/ to _vendor/ if you want to ignore them temporarily.

(afaik) He retired around the Go 1.0 release, though he showed up as unixken on reddit during a Go Ask Me Anything.

https://www.reddit.com/r/golang/comments/46bd5h/ama_we_are_t...

Until you have users. :-P

For one example, check this comparison: https://dockyard.com/blog/2016/08/09/phoenix-channels-vs-rai...

The only problem is that you need to maintain and enhance that MVP for the next several years -- unless it's just a hackathon.

I've spent way too much of my life trying to optimize Ruby performance and memory usage, switching from one web server to the next, then fixing threading issues in dependencies, and so on. It's not fun. All that upfront productivity is lost in the end.

Quite happy to spend more time upfront investing in a reliable end-product.

There was also the matter of figuring out llvm in order to use it. The initial Go compiler was based on the Plan 9 C compiler toolchain, which the designers of Go know well.

One of the other reasons relates to how stacks are handled for goroutines.

You can read through this thread to see what people want to work on for Go 1.8.

https://groups.google.com/forum/#!topic/golang-dev/098vr4999...

There are active discussions on the Go Package Management mailing list and the intention to propose further improvements to the go toolchain for future releases. We had good discussions with the Go Team during GopherCon last month.

https://groups.google.com/forum/#!forum/go-package-managemen...

If it works in Go 1.5.3 but not Go 1.6, definitely consider filing an issue. https://github.com/golang/go/blob/master/CONTRIBUTING.md

The SSA branch is for a future version of Go, possibly Go 1.7.

404 when clicking this link.

There is a Go AMA on reddit for the next 24 hours.

https://www.reddit.com/r/golang/comments/46bd5h/ama_we_are_t...

Go 1.6 beta1 and Apple's new HTTP/2 push notification service both were released today. What timing!

I've begun work on a Go 1.6+ APN library that uses HTTP/2. You can find it here: https://github.com/RobotsAndPencils/buford

This article is an excerpt from Learn Go, a beginner's guide to Go, that I am writing with Manning Publications.

I'm targeting people with some experience with a scripting language but fairly new to programming, while trying to keep it moving at a good pace. If that describes you, I'm very curious if it makes sense or what areas should be better explained.

If you are new to Go and statically compiled languages in general, I've been working on a book to introduce you to Go.

The first two chapters are now available through Manning. Use mlyoungman to receive 50% off through October 17, 2015. This affiliate link earns me a few extra %. Thanks.

Smart!

I'm really curious to give Gerrit a try. Is it like the existing Rietveld system used for Go?

- I've been using the "apply mail" flow to avoid merge commits and to squash commits when appropriate (based on Nathaniel Talbott's post http://blog.spreedly.com/author/ntalbott/#.VGVhz5PF_Zs). It will be nice to have something automatic.

- At least contributors with the commit bit can just create a feature branch and a pull request from there. Some open source projects give out the commit bit almost immediately, but with GitHub there's still that initial fork and pull request to prove oneself.

Interested to see how Gerrit addresses this. GitHub doesn't have any way to disable pull requests. :-(

- I've completely disabled email notifications for this reason. There still can be a huge number of notifications in app or via third-party mobile apps. Rietveld is a lot more sane, I only saw notifications for things I was actively working on.

- I usually end up reviewing just the new commits individually. But that requires figuring out which ones I had already reviewed. Not so bad with only a few branches, but I can see it getting out of hand.

I really hope people from GitHub are reading this thread as they are working to improve their tools. :-)

The code is identical on GitHub and Google Code right now. The difference is that we may make breaking changes under go.exp while leaving the howeyc/fsnotify API as is.

We're still figuring out what os/fsnotify will look like.