![]() I later moved to Java and finally Scala (with some Go in between) and recently started learning Rust. I then used Ada and C/C++ when I started working in the early 90's. ![]() My first significant programs were written in Pascal. Some background: I love statically typed languages. As my side project was a simple API I thought using Go would be the right tool to get the job done quickly, but as we know many projects grow beyond their initial scope, so I had to write some data processing to compute statistics and the pains of Go came back. The network part was rather pleasant (I was also discovering the language), but the accounting and billing part that came with it was painful. I used Go extensively in my previous job to write a network proxy (both http and raw tcp) for a SaaS service. What motivated this post is that I recently came back to using Go for a side project. But even for network programming, it has a lot of gotchas both in its design and implementation that make it dangerous under an apparent simplicity. Go does have some nice features, hence the “The Good” part in this post, but overall I find it cumbersome and painful to use when we go beyond API or network servers (which is what it was designed for) and use it for business domain logic. This is an additional post in the “ Go is not good” series.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |