11–20 of 168 posts
This is great news. The best part of it for me is that now my more conservative colleagues might dip their toes in the water. Combine that with the Vitess project and Go is not just a great language. It's viable.
If anyone from the Go team reads this, http://golang.org/doc/go_tutorial.html linked to from the blog gives a file not found error.
If anyone from the Go team reads this, http://golang.org/doc/go_tutorial.html linked to from the blog gives a file not found error.
If anyone from the Go team reads this, http://golang.org/doc/go_tutorial.html linked to from the blog gives a file not found error.
It provides an interactive in-browser panel to try out the language while presenting its features.
FWIW, the go dashboard (https://godashboard.appspot.com/) has a number of interesting projects.
Been playing with the weekly versions of Go for a couple weeks now. Highly enjoying it, my biggest pet peeve was that every library had a master and "weekly" branch which required me to manually pull down the weekly. Shouldn't be long and I can move to master!
Doesn't go tool handles that automatically (i.e. checks out the most recent tag compatible with the current Go version)?
I figured their had to be a better way but I was pretty focused on getting projects done.
And to be specific this was on non-standard libraries the standard libraries provided by go worked out of the box.
I foresee the next version being considered harmful.
Can we now say that Google Chrome can be written in Go and it will be faster and/or stable ? ( not saying it is not already. ).
Congrats to the team, just started using go yesterday and loving it.