Earlier quoted context omitted.
I was about to say the same thing. Go is popular because it's initiated and backed up by Google.
If that were enough Angular would be more popular than it is.
The Go Programming Language and Environment
21–30 of 250 posts
Re: The Go Programming Language and Environment
#22I’m pretty sure the Google name association can explain the languages popularity. I remember reading novices wanting to learn Golang due to the Google name attachment. That propelled the language into many minds, especially new programmers.
Re: The Go Programming Language and Environment
#23Earlier quoted context omitted.
I was about to say the same thing. Go is popular because it's initiated and backed up by Google.
If that were enough Angular would be more popular than it is.
Besides, being backed by a $CORP is necessary condition but not a sufficient condition for a language to become mainstream.
Re: The Go Programming Language and Environment
#24Re: The Go Programming Language and Environment
#25* "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".
- Stable middle-class upbringing. Ah, I remember how nice it was to decompress at our summer house in Tuscany.
Re: The Go Programming Language and Environment
#26* "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 makin…
Re: The Go Programming Language and Environment
#27What I'm more interested in is the comparison between the cases of Go and Dart, which both are languages developed by Google. Why Go is so much more successful (in the system programming domain) than Dart (in the web/mobile/desktop domains)? Many of the listed good choices (e.g. being developer-focused) can be (had been?) applied to Dart as well.
Go brought something new that answered an issue developers were facing: easy concurrency in a high performance garbage-collected language that compiled to a single binary with no dependencies. C/c++ did not offer that, nor did java, nor did python. Go filled the gap in the market.
Re: The Go Programming Language and Environment
#28The 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
#29The 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.
Like Go, C# has also always been a decade behind on the tooling side. For a recent project I wanted very fast HTML templating and I/O. Went with C# instead of Go and it's looking pretty good so far. The tooling is close to the level Ruby was ten years ago, and that was really acceptable. I was very happy with my previous project that I did in Go as well, you just can't go wrong with Go for implementing network protoc…
Note: not trying to pick a fight, I'm legit interested what I might be missing since I feel like my needs are pretty much covered :)
Re: The Go Programming Language and Environment
#30I think it misses * Made by really famous veteran language designers * Backed by Google Not saying it doesn't deserve its popularity, but most of the things listed are not necessary for explaining its popularity, and none of them (even taken together) are sufficient.
Go is very well documented: That was the killer feature for me.
No more search tutorials / videos etc. - just get the go book, read it, and start coding.
Of course there are tutorials and videos everywhere for fun stuff.
But good documentation is more important than we think - even in the 21st century!