Why Go is doomed to succeed
texlution.com
Why Go is doomed to succeed
1–10 of 330 posts
Re: Why Go is doomed to succeed
#2Re: Why Go is doomed to succeed
#3Re: Why Go is doomed to succeed
#4Re: Why Go is doomed to succeed
#5Re: Why Go is doomed to succeed
#6Very true.
This article hits the nail on the head. Most people say that they cannot "express" certain things in go, or have to jump through hoops to do it. The point of go is not to create a highly expressive language, but rather to create one that has a high enough abstraction to be productive but simple enough so that people coming from different backgrounds can acquaint themselves with it quickly.
In other words, it is a language for teams.
Re: Why Go is doomed to succeed
#7Re: Why Go is doomed to succeed
#8> TL;DR Golang was explicitly engineered to thrive in projects built by large groups of programmers with different skill levels, and there is no larger such group than the open source community. Very true. This article hits the nail on the head. Most people say that they cannot "express" certain things in go, or have to jump through hoops to do it. The point of go is not to create a highly expressive language, but ra…
Re: Why Go is doomed to succeed
#9Compiled to native binary, garbage collected, no JVM and not object oriented is why I like it.
Re: Why Go is doomed to succeed
#10Because the Unix system programming world (and POSIX particularly) is very much built with the conventions and semantics of C in mind, most serious POSIX programming outside of C means you have to deal with painful FFIs, lousy wrappers, overly abstracted APIs that hide details like certain lower level flags and so forth. Some are better at this than others, of course (OCaml is one of the better ones)... but, nonetheless.
So it's unsurprising that many infrastructure developers are jumping to Go. There's just enough new things to incentivize a switch, but not too much that it dissuades from it.