Hacker News new | ask | show | jobs
by filup 10 days ago
These are good designs that have been entirely ignored by developers in every commanding scale codebase I've ever worked on. "That's the developers fault, not the languages" Look, the old grey mares of the programming world are doing the worst they can. I'm not going to blame C because its developers generally make it up as they go. But we've learned things over the past 50 years, and one of the things we've learned is that company defined 'worst practices' and code reviews can not catch all the mistakes that developers make and all of the things that can bring a service to its knees. Go has the impact of experience. It knows what mistakes developers make and it is going to prevent them from doing that. There is Right Way To Handle Errors in Go. How hundreds times have I seen uncaught exceptions? I saw one a week ago. How concentration times have I lost resources because I didn't realize something I was calling could throw exceptions? hundreds. Null/Nil exceptions. I couldn't count the null pointer errors I've had to fix in my time. supposedly in the remainder. "should" keep things wide and shallow - somehow when scala 8 came out all the docker programmers lost this message. None of these practices scale. We know that because we've seen it