I&#x27;ve done real-life web dev using PHP and using Go, and have dabbled with Node.  Thoughts:<p>1. Go&#x27;s strict, statically typed, thou-shalt-check-thy-errors approach is a breath of fresh air.  The compiler does a whole load of checking which can (and therefore should) be automated, which in many other languages is left to the developer.   Go code tends to have the property that if it compiles, it probably works as designed.  I love this.<p>2.  IMHO it makes more sense to think of a web app as a server application one of whose functions is to listen for and respond to HTTP requests.  So, the question I&#x27;d ask is &quot;is this a good language for server programming, and how easily can I make it speak HTTP?&quot;  In Go&#x27;s case I&#x27;ve found the answers to be &quot;hell yes&quot; and &quot;very&quot;.<p>3. The tooling is really nice.  go fmt takes a whole load of pain away from everyone (no more effort required to format code properly, the tab&#x2F;space and where-to-put-the-{ debates are solved decisively, reading other people&#x27;s code is made easier), the package management is lovely, statically-linked executables are easy to move around and go doc encourages proper commenting.<p>4. Really good performance.<p>5. The biggest drawback I&#x27;ve seen with Go is verbosity - although a lot of the time it turns out that my verbose Go code is checking errors properly and my compact PHP code wasn&#x27;t.