>>105645913
This is not true in the slightest. OpenBSD developers fuck up all of the time. But thanks to there being a lot of people in the community checking diffs and giving advice bugs like this are generally caught before they get anywhere near current snapshots. Never mind how scrutinized everything gets again before it gets shipped as stable.
People fuck up all of the time. The difference between something like this example and most other "developers" for major projects is he was willing to admit his mistake and fix it. Instead of defending it like a retard. The only people I trust are people willing to admit mistakes.
I once fucked up badly and shipped out a piece of code with '=' instead of '==' within an if condition. It was a stupid typo but thanks to the language I was using the error passed right through and the software worked as intended most of the time. It wasn't caught for weeks until someone actually managed to hit the one trip through the loop where it caused an issue. He reported it, I admitted my dumb mistakes caused by writing code on no sleep for 3 days at 4am in the morning. I shipped out a patch+bumped release to 1.0.1 within an hour or so. Most people didn't even notice and lots of people still run the buggy original release because even 25 years later they refuse to update since the original release
>just werks.
You people can fear monger and cry all you want. Even if he couldn't write code at all having him in charge of the repo is much better than what we had before. You're not going to convince anyone that our machines are going to be exploited because
>muh spooky X server can connect to the internet
when most people have that disabled without even being aware of it. Since no one has shipped Xorg with networking support enabled in decades now. It's only turned on by people that still need it and it still works fine. Plus there is a lot of room for improvement on that front that I'm looking forward to seeing happen in an active fork.
