It's not about who wrote that code. It's about responsibility. If you are the maintainer of shitty code, then at the very least communicate that publicly. Don't

It's not about who wrote that code. It's about responsibility. If you are the maintainer of shitty code, then at the very least communicate that publicly. Don't come out with how bad your code is after the fact! After he was responsible for that code for years, he now goes public and matter of factly states that all the code was shit the whole time. Well why didn't he do anything about it then? What did he think the job description of being maintainer entailed? Filippo wasted no time shitting on other crypto projects, like GnuPG, from what then looked like the high ground. And now he leaves Google and by the way the supposed high ground was an optical illusion (and that's the charitable phrasing). My theory is that you people like this kind of story because it helps you cope with your own mediocrity. If Google and Golang have this kind of laissez-faire approach, why should I have higher standards? We'll just call it a life lesson as if it was handed down from heaven, as if things HAD to be this bad. Sprinkle some "bugs happen to anyone" and "you can't have 100% security anyway" on top and your shit burger is finished. Now feel free to downvote me, you hypocrites!