Skip to content

Commit 638f20f

Browse files
committed
Remove comparison with argon2-ffi from README
1 parent e0bb8fd commit 638f20f

File tree

1 file changed

+0
-18
lines changed

1 file changed

+0
-18
lines changed

README.md

-18
Original file line numberDiff line numberDiff line change
@@ -148,24 +148,6 @@ you'll need to specify that in the command.
148148
This seems to be an issue related to snap (see [#345 (comment)](https://github.com/ranisalt/node-argon2/issues/345#issuecomment-1164178674)). Installing Node with another package manager, such as [asdf](https://asdf-vm.com/) or [nvm](https://github.com/nvm-sh/nvm), is a possible workaround.
149149
</details>
150150

151-
### Differences from [node-argon2-ffi](https://github.com/cjlarose/argon2-ffi)
152-
The interface of both are very similar, notably, node-argon2-ffi splits the
153-
argon2i and argon2d function set, but this module also has the argon2id option,
154-
which node-argon2-ffi **does not support**. Also, while node-argon2-ffi
155-
suggests you promisify `crypto.randomBytes`, node-argon2 library does that
156-
internally.
157-
158-
**node-argon2** is much lighter than **node-argon2-ffi**, at 184 KB for
159-
[email protected] against 2.56 MB for [email protected]. Performance-wise, the
160-
libraries are equal. You can run the same benchmark suite if you are curious,
161-
but both can perform around 130 hashes/second on an Intel Core i5-4460 @ 3.2GHz
162-
with default options.
163-
164-
This library is implemented natively, meaning it is an extension to the node
165-
engine. Thus, half of the code is C++ bindings, the other half is Javascript
166-
functions. node-argon2-ffi uses ffi, a mechanism to call functions from one
167-
language in another, and handles the type bindings (e.g. JS Number -> C++ int).
168-
169151
## Contributors
170152

171153
### Code contributors

0 commit comments

Comments
 (0)