Live data from Hacker News

The Go Programming Language and Environment

cacm.acm.org

1–10 of 250 posts

Re: The Go Programming Language and Environment

#3
* "easy" concurrency

* rich standard library, particular for internet facing apps

* "simple" language

* single binaries

* massive corporate support

* rich or full toolset

The first and second point fortunately "coincided" with: the move to multi-core chips, and the "second" dot.com boom of the 2010s. Which you could probably attribute to the rise of (Google) Chrome, and the decline (finally!!) of IE6, which held back a lot of "innovation".

Re: The Go Programming Language and Environment

#5
The CTO dictated our move to Go two years ago on what felt like a combination of whimsy and anti-Microsoft sentiment. I'll admit that there are parts of the language that are nice, such as the relatively snappy compile times and single statically linked binary output, but not a single day goes by where I don't miss C#, and more specifically .NET Core (now just .NET I guess?), which can do everything Go is doing.

Re: The Go Programming Language and Environment

#6
post #5

The CTO dictated our move to Go two years ago on what felt like a combination of whimsy and anti-Microsoft sentiment. I'll admit that there are parts of the language that are nice, such as the relatively snappy compile times and single statically linked binary output, but not a single day goes by where I don't miss C#, and more specifically .NET Core (now just .NET I guess?), which can do everything Go is doing.

Yeah, the language itself has never really “clicked” for me, and I've tried a few times. It still feels cumbersome to write. The tooling, standard library and fast compile times are really great though. Maybe I'll revisit it.

Re: The Go Programming Language and Environment

#7
post #3

* "easy" concurrency * rich standard library, particular for internet facing apps * "simple" language * single binaries * massive corporate support * rich or full toolset The first and second point fortunately "coincided" with: the move to multi-core chips, and the "second" dot.com boom of the 2010s. Which you could probably attribute to the rise of (Google) Chrome, and the decline (finally!!) of IE6, which held back…

I'd add "well designed" to the standard library point. When I first started using Go, one of the things that struck me was that not only was there tons of standard library functionality to do things I'd normally have to install 3rd party modules for in other languages, but those standard library modules (mostly) had well-designed, easy-to-use, and consistent interfaces. Mostly. I'll still never forgive them for making crypto.PublicKey an empty interface.

Re: The Go Programming Language and Environment

#9
post #3

* "easy" concurrency * rich standard library, particular for internet facing apps * "simple" language * single binaries * massive corporate support * rich or full toolset The first and second point fortunately "coincided" with: the move to multi-core chips, and the "second" dot.com boom of the 2010s. Which you could probably attribute to the rise of (Google) Chrome, and the decline (finally!!) of IE6, which held back…

This reads exactly like the joke where successful people describe their daily routine and one of the items besides things like running and meditating once a day is "my parents are millionaires".

Re: The Go Programming Language and Environment

#10
Apart from the concurrency benefits, Golang provides actual value like C or C++.

Therefore it got popular without incessant propaganda and a large consultancy ecosystem (unlike Python, which relies on brutal marketing: There are basically two uninteresting syntax posts on the front page every day, just to keep the brand recognition going).

Post reply on HN