am very happy the author is happy with go. >>Deploying Go code to production is as simple as copying a single binary file up to a server and running it. No rev

am very happy the author is happy with go. >>Deploying Go code to production is as simple as copying a single binary file up to a server and running it. No reverse proxies, no dependencies to install on the target server, no class paths. Just copy the binary and run. This fairly depends size of system we are discussing. >>Some developers have noted Go’s lack of features or a few other things: no exceptions, nils instead of options, inability to specify dependency versions, mark and sweep GC, no macros, no generics. languages such as Java too grew out from such weaknesses and are still growing >>If I were a developer getting started today, I’d make a career bet on Go. Fairly good but it depends on what market attracts you.For e.g. if you were to target financial markets with big responsive systems , i doubt if they have loads of Go lang hires vs the same on say Java hires.But if we were to target a different market,it would change too!