3 ms·
Since Go is fairly abstraction-resistant, you end up declaring API's for concrete things. For example, there is not much point in writing a generic Set class.
by skybrian 10y ago
Since Go is fairly abstraction-resistant, you end up declaring API's for concrete things.
For example, there is not much point in writing a generic Set class. There are lots of packages available but they tend to solve concrete, domain-specific problems. The difference between this and the typical Haskell library where you need to be mathematically sophisticated to even know what problem it solves is pretty stark.
It would not be my favorite language for writing a compiler for an evolving language. But for scripts and simple servers it's pretty good.
- codygman 10y ago> The difference between this and the typical Haskell library where you need to be mathematically sophisticated to even know what problem it solves is pretty stark. I'm a Haskell developer and the most math I know is algebra 2. I also don't have a degree. I write Go for work. You don't need to know much math for Haskell. Go's lack of generics is a HUGE mistake and bites my teammates and I often.