The ecosystem of the Go programming language
Go is not a simple language. Please learn from my mistakes, and ignore arbitrary metrics like how go has fewer keywords. The complexity doesn&#x27;t go away, it&#x27;s hidden away somewhere.<p>If anybody wants to learn go, ignore everything about how easy it is to learn. Because it&#x27;s extremely deceptive. Take time to actually read through a lot of the important underlying concepts like how slices work.<p>Ignore comments about how go is simple to write. There&#x27;s a fair amount of bad go code and people break rules all the time. From official sdks to standard libs. Go can be extremely difficult to both write and read. It&#x27;s implicit interfaces and judicious abuse of interface{} can make tracing how a library is supposed to work a PITA. Writing go can be difficult because of a lack of some language constructs that leave you unsure how to proceed.<p>If you can, use goland. I use vscode and it&#x27;s... not pretty. Almost every single thread I&#x27;ve seen on reddit recommends goland. My experience with vscode has been very unpleasant, particularly with go plus.<p>OTOH, things like criticisms about it&#x27;s error handling are overblown. At best it&#x27;s a mild nuisance, and more often than not, a good thing that makes error handling explicit and clear.<p>There are many things about go that have made me appreciate it&#x27;s existence. There are also many things that have left me absolutely baffled at how bad it is.