Hacker News new | past | comments | ask | show | jobs | submit login

I've been working professionally in Go for almost a year now and I do agree Go is really pragmatic and is largely nice for just "getting stuff done".

However there is an absurd amount of nil checking which can be easy to miss and not always caught by the common linting tools. Once you use Result/Option types and proper enums with pattern matching that is expressive and safe, it wears on you that Go does not have this.




> it wears on you that Go does not have this

And it's a completely unforced error and doubled-down on by the development team.


Where did they double down on this? They explicitly said that the design of generics was leaving the door open for sum types.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: