I can't work on both simultaneously. As libsodium has become pretty much feature complete, and much more bloated that I initially wanted, I am now refocusing mo

I can't work on both simultaneously. As libsodium has become pretty much feature complete, and much more bloated that I initially wanted, I am now refocusing more on hydrogen. Since this is relevant to the original topic, the password hashing API is a good illustration of the difference between both libraries. New additions to libsodium must remain consistent with historic APIs, that have limitations and usability issues. Hydrogen learned from this, and tries to model its API after common problems to solve in real-world applications rather than provide interfaces to cryptographic primitives. This will eventually become the base of libsodium 2.x Of course, there's nothing wrong with using libsodium, if only because it's way more mature and implements conservative designs that you can trust. But feedback on Hydrogen would also be really great. I really want to avoid doing the same mistakes again, and build the best possible easy-to-use hard-to-misuse APIs that everybody can use confidently.