5 ms·
I really liked that read, good writing style and the author was coming from the same place that I'm usually coming from (can we redo this ourselves and shave of
by fefe23 9y ago
I really liked that read, good writing style and the author was coming from the same place that I'm usually coming from (can we redo this ourselves and shave off some bloat in the process).
However, as it stands now, it looks more like a cautionary tale on why he should have listened when people told him not to do it :-)
I suspect a worthier goal would have been to look for ways to improve the linking footprint of libsodium instead of rolling your own library. Maybe turn the "I want the smaller version without the huge lookup table please" in a compile time option or so. That way more people could have used it without having to commit to "I'll use this little known experimental library instead of libsodium". Commit in the sense of "people will ask why and I will have to defend my decision", not in the sense of "oh no we are locked in!!"
- loup-vaillant 9y agoReducing the linking footprint wasn't my only goal. Reducing the source code is also important, if only to facilitate tests and audits —thus increasing confidence. That huge table for instance would need to be tested. Every single value would need to be checked for correctness, or I would have to demonstrate they came from a sound generator. --- I've been careful not to lock people in. If people want to upgrade to faster primitives, they can. I don't think they will ever need to, though.