> He picks an arbitrary design constraint, in this case correctness, and argues that any language that does not provide 100% correctness is bad I'm sorry, WHAT

> He picks an arbitrary design constraint, in this case correctness, and argues that any language that does not provide 100% correctness is bad I'm sorry, WHAT? This is not about correctness (and IMHO if you have something that makes this tradeoff you should not use it anyway), it's about pretending that correctness does not matter and that unexpected bad behavior is okay... cause you know 80/20. IMHO Go has its use cases but it's definitely not a panacea. I don't mind people pragmatically picking it and using it. I am bothered by the zealots that think this is the best thing since sliced break (spoiler alert: it's not). Its authors and the community also seem to have an elitist / better than you default attitude when being humble and open would actually serve them better (package management and generics come into mind - what disasters)