2 ms·

In many application use cases, that is an implementation detail that should not be a concern of higher levels. The ramifications may not even be known by the pe

In many application use cases, that is an implementation detail that should not be a concern of higher levels. The ramifications may not even be known by the people at higher levels. Take something very common like cryptographic hashing, if you use something like node.js you really don't want to block the main thread calculating an advanced bcrypt hash. It also meets all of your requirements that data not come from outside ram and is very CPU bound. Obviously, if you are directly calling this hashing algorithm you should know, however, the introduction of a need to hash is completely unpredictable.

gwbas1c 2y ago
> Take something very common like cryptographic hashing, if you use something like node.js you really don't want to block the main thread calculating an advanced bcrypt hash. It also meets all of your requirements that data not come from outside ram and is very CPU bound. I guess I implied quick operations when I said "CPU bound." (IE, calculating a square root, string manipulation, (de)serialization...) I haven't done hashing in Node.js. I assume that the bcrypt API is async and calls into a native library?