3 ms·
The author could have avoided all this pain by reading effective go and avoided panics like they recommend.
by marcrosoft 6y ago
The author could have avoided all this pain by reading effective go and avoided panics like they recommend.
- ebiester 6y agoThe author was working with a codebase they didn’t write to start with, as stated in the article.
- gonzo41 6y agoRookie mistake, Always insist on a rewrite. :p
- sigzero 6y agoOr maybe you could have read the article and realized the author inherited a codebase and wasn't the Creator of it.
- cambalache 6y agoBut then the problem was not the language but the people who worked with it. This could happen with every language, even the venerable holy grails.
- DangitBobby 6y agoOnly if you ignore that it is the language design that encouraged the choices in the offending codebase that the author laments having to change.