7 ms·
> What's petty about removing bad code? Nothing. But no one said anything about removing bad code. Have you looked at that page? Their comments are extremely
by coldpie 12y ago
> What's petty about removing bad code?
Nothing. But no one said anything about removing bad code.
Have you looked at that page? Their comments are extremely rude:
"So the OpenSSL codebase does “get the time, add it as a random seed” in a bunch of places inside the TLS engine, to try to keep entropy high. I wonder if their moto is “If you can’t solve a problem, at least try to do it badly”."
"Old news, but OpenSSL doesn’t give a fuck whether or not memory was freed. It’s all good."
It's hostile, unprofessional, and unnecessary. I understand these kinds of comments in a private IRC channel or something, but publicly ridiculing someone else's software, especially mission critical software that's been used for years across many platforms, is uncalled for.
It really gave me a bad taste for the LibreSSL project, and all just for some petty sniping.
- e12e 12y ago> It's hostile, unprofessional, and unnecessary. It might be "unprofessional" which is to say, it's not polite (and since they're giving it away - why would it be "professional" -- they're not (necessarily) getting paid for the work) -- but it's not really disproportionately hostile, and most of all, I disagree that it's "unnecessary". As evidenced in part by recent security issues, and in part by what the libressl project has dug up/cut away: the code base was horrid for the purpose (providing authentication and confidentiality). Much worse than merely "not good". I think the (rightfully) hostile attitude helps others realize just how bad things were/are. And I welcome it. I'm sure a few developers are hurt by the comments, but all of your quotes above are pretty much factual and concrete: it's not name calling for the sake of being rude; it's a wake-up call. I'd be surprised if not a few "victims" of those comments aren't also glad that errors are both found and pointed out. Just as if you hacked together a not-quite working break system for a car, you'd prefer being called out as a hack, and someone fixing it, rather than having lots of people get hurt. The stakes involving openssl can actually be life or death.
- jdbernard 12y agoAgreed. There is a place to be gentle towards others' code, but security is one of the areas where we shouldn't care a mote about developers' feelings, only about the quality of the code.
- TheCondor 12y agoSo being rude is what you do if it's "important" and the other party didn't have an optimal solution? Looking at the long history of openbsd and some similar projects, I think being rude like that is what you do when you're too far on to the spectrum to effectively articulate an argument. It probably has something to do with lack of empathy as well... There are very real reasons why their project and user base is the size it is.
- deleted 12y ago[deleted]
- x0x0 12y agoopenssh has incredibly broad usage
- e12e 12y ago> So being rude is what you do if it's "important" and the other party didn't have an optimal solution? No, being direct is what you do if it's important. I agree that the above quotes aren't polite, but I don't think they're terribly rude. If I publish half-assed code that is hopelessly structured (even if there are reasons for it; "There's too much old cruft", "I don't have time to ...") -- I wouldn't mind getting called on my bullshit. If you suck, and someone point out to you, that you do, in fact suck -- then you should thank that someone. Sure, it might be nicer if they're polite about it -- but it's really not that big of a deal.
- coldpie 12y agoI work on an open source project in my dayjob, and I can tell you I'd be far less inclined to work with an individual who curses at other developers and makes tons of disparaging comments about my work or the work of others. It creates a hostile and unwelcoming environment, which is not the kind of environment I want to be in.
- clarry 12y agoGood news in this case: you're not obliged to subscribe to source-changes@openbsd.org. Nor is anybody else... you don't even have to dig the archives or the third party blogs that publicize the commits. But those who follow the commits know that the developers like to express their minds in the commit messages whether it is bad code written by one of them or somebody else. They're not targetting and publicly shaming some project while throwing insults straight at developers.
- e12e 12y agoBut there was no cursing at other developers in the above quotes? It was some mild (and justified) ridicule. And an implication that they didn't give a fuck -- which might be a little crude. But it's kind of hard to argue that it might not be accurate criticism.
- PopsiclePete 12y agoYou're obviously not a "rock star" or "code ninja" then. What's next, you're not going to have tits in your slides ???
- ikt 12y ago> I think the (rightfully) hostile attitude helps others realize just how bad things were/are. Linux creator Linus Torvalds has labeled makers of the OpenBSD operating system a "bunch of masturbating monkeys," http://news.cnet.com/Torvalds-attacks-IT-industry-security-circus/2100-1007_3-6243900.html http://news.cnet.com/Torvalds-attacks-IT-industry-security-c... I completely understand what he was talking about now.
- mrweasel 12y agoIt may be hostile and unprofessional, but it is necessary. Given the OpenBSD developer have been able to pull a number of important patches directly from the OpenSSL bug tracker and fix issues in LibreSSL, it's clear that polite and professional didn't work either. Would you have known that parts of the OpenSSL code base was so badly (and unprofessionally ) implemented if the OpenBSD developers hadn't been somewhat aggressive?
- Dewie 12y ago> It's hostile, unprofessional, and unnecessary. Well I guess you do what's normal when you think someone is being unprofessional: stop buying their products and stop doing business with them. Oh wait...
- njharman 12y agoIt's punishment, it's shamming, and it is absolutely necessary. It will discourage poor programmers and great programmers who don't know enough about security from half-assing critical software.