Wonder where they'll go once their codebase becomes crippled with interface{} type and nil pointers check, and they stop using chanel to return to mutex for performance reasons, or more control.
Note : sounds snarky, but it's an honest question i find asking to myself after having tried many server side techs and feeling limited with go.
1) I have a totally different experience ! When your are writting code which must have a certain degree of genericity you end up having a ton of interface{} …
2) wat ? How having a null pointer a non issue ?! Empirically it causes fewer bugs than in Java or JavaScript, but it's still a really common source of bugs in Go.
3) I've never run into this kind of problem myself since I dont use Go for performance-heavy code.
Note : sounds snarky, but it's an honest question i find asking to myself after having tried many server side techs and feeling limited with go.