Live data from Hacker News

Half a decade with Go

blog.golang.org

1–10 of 257 posts

Re: Half a decade with Go

#2
Crazy that it has been 5 years. Time flies when your having fun.

The golang team has done a fantastic job. It is now my primary language of choice to get things done.

2 years ago I started playing with it moderately, and now in the past 12 months or so it has made its way into my normal workflow and have been delivering completed projects in golang.

I am excited for the next chapter in golang. Keep up the good work!

Re: Half a decade with Go

#4
> , we were calling Go a "systems language"

And maybe in another 5 years, people will stop bickering over whether that description is/was appropriate. :)

Re: Half a decade with Go

#6
post #2

Crazy that it has been 5 years. Time flies when your having fun. The golang team has done a fantastic job. It is now my primary language of choice to get things done. 2 years ago I started playing with it moderately, and now in the past 12 months or so it has made its way into my normal workflow and have been delivering completed projects in golang. I am excited for the next chapter in golang. Keep up the good work!

I've been using it instead of Python as my custom analysis tool - the ease of concurrency makes it very handy when working with large data sets, or gluing various codes together.

Re: Half a decade with Go

#7

Shameless promotion in case you don't read OP. We're posting an article every day on blog.gopheracademy.com celebrating the use of Go around the world. http://blog.gopheracademy.com/birthday-bash-2014/go-turns-5/

[deleted]

Re: Half a decade with Go

#10
At launch, there was a flurry of attention. Google had produced a new programming language, and everyone was eager to check it out. Some programmers were turned off by Go's conservative feature set—at first glance they saw "nothing to see here"...

This was totally me. I am very much a programming language aficionado (or maybe just a dilettante), and when I first read about Go, I dismissed it quickly. I'd mostly been using Lua at the time, and didn't really understand what was different with goroutines vs. coroutines.

After the initial release, it took us a while to properly communicate the goals and design ethos behind Go. Rob Pike did so eloquently in his 2012 essay Go at Google: Language Design in the Service of Software Engineering and more personally in his blog post Less is exponentially more. Andrew Gerrand's Code that grows with grace (slides) and Go for Gophers (slides) give a more in-depth, technical take on Go's design philosophy.

It was Rob Pike's essay that caused me to investigate it again.

I have been quite impressed with lots of little details that have been 'fixed' (relative to C) in Go. Such as how variables are declared, the module system, and much more. And I was and continue to be impressed with the associated tooling.

I hope that if Go has just one lasting legacy in the history of programming, it will be how it pushed forward people's expectations of what a good language ecosystem should provide.

Post reply on HN