3 ms·
I really wish there weren't two popular projects that were abbreviated to NaCl. For others, this is a port of the "salt" NaCl crypto library, and has nothing t
by kibibu 12y ago
I really wish there weren't two popular projects that were abbreviated to NaCl.
For others, this is a port of the "salt" NaCl crypto library, and has nothing to do with Native Client.
The dangers of JS crypto in the browser are well trodden (anybody who can snoop the connection can probably replace the JS, for example), but the rise of JS-based client apps (through node-webkit et al) make this a bit more meaningful.
- hayksaakian 12y agothank you for clarifying. Sometimes these name collisions don't matter because the projects are from two separate groups of software, but in this case, the overlap in 'client facing web apps' makes NaCl downright confusing without clarification.
- CmonDev 12y agoYes, I was initially excited expecting to see something awesome for Google NaCl, but it turned out to be yet another script written in a legacy language... Well, he did add .js to the name though.
- xiaoma 12y agoWhat exactly are you referring to with "legacy language"? Could you elaborate?
- kibibu 12y agoI'm pretty sure it was just snark at Javascript/ECMAscript. IMO it's pretty hard to justify calling it a legacy language when there are 4 major JS JIT engines actively competing for performance, and a pretty thriving developer ecosystem. It's about as young as Ruby, and younger than Python and Haskell.
- nly 12y agoAfaik NaCl from DBJ et al. isn't actively maintained, by them, as an ongoing project. It hasn't been updated since early 2011. libsodium is where it's at now. Going forward, I wouldn't expect TweetNaCl to be either so there's not much of a naming collision.