New case studies about Google’s use of Go
I played around with Go a while ago, and while I appreciated the approach to concurrency, I was really put off by both the boilerplate + how primitive the type system felt. Not having map and filter due to lack of generics meant writing for loops all over the place just to filter and modify arrays. Appending elements to slices felt clumsy. The type system didn&#x27;t feel expressive, and I often found myself having to resort to the empty interface escape hatch.<p>Compare this with Typescript (or Swift, or Rust), which have type systems capable of modeling nearly any problem domain. Go doesn&#x27;t have algebraic data types (sum types) which are incredibly useful in my experience (Swift&#x2F;Rust enums, Typescript discriminated unions). I&#x27;m honestly not sure why I would use Go over TS, unless performance was my primary consideration. It feels like Go was designing to be as inoffensive as possible to a legion of new-grad Google programmers, and you sacrifice most modern language niceties for it. Please convince me I&#x27;m wrong, because I really wanted to like Go.