News for hackers. Stuff that matters.
Re:Ask HN: When does it make sense to roll your own X? by dpratt on Sunday July 14, 2019 @01:34AM (#20431836)
You’re likely being downvoted due to the pithiness of your comment, but you make an excellent point. I’ve always promoted the three Iron Laws of never implementing

1) Encryption 2) Date/time math 3) Distributed locking/concurrency primitives

All of these are of sufficient complexity to virtually guarantee that you’re going to miss a score of subtle edge cases, and the consequences thereof are likely simultaneously pervasive, silent and catastrophic.

Re:Ask HN: When does it make sense to roll your own X? by _Nat_ on Sunday July 14, 2019 @02:16AM (#20431951)
Some of the downvotes may be from crypto-programmers' frustrations, too.

I mean, obviously, someone has to code crypto, or else it wouldn't exist. But, whenever you try talking about the topic online -- whether you're doing it professionally or for self-education -- a probably well-meaning chorus of spam comments warn against doing anything.

I suspect that some crypto-folks have given up rebutting the don't-roll-your-own stuff and just down-vote reflexively.

Re:Ask HN: When does it make sense to roll your own X? by Gibbon1 on Sunday July 14, 2019 @02:56AM (#20432090)
My frustration with don't write you own is you get strongly urged to use either libraries that are nothing but a tinker toy set of primitives. Or sudo apt-get install openssl.
Re:Ask HN: When does it make sense to roll your own X? by polskibus on Sunday July 14, 2019 @06:19AM (#20432695)
Which open source distributed locking libraries would you recommend?