(❗️❗️❗️已经不维护了)It is no longer maintained, so there is no need to raise issues 😂
shylock-wu opened this issue · comments
It is no longer maintained, so there is no need to raise issues 😂
说明文档里面说“It is time to go for the native crypto module”，但是我不认为使用原生的 crypto 模块在目前来说是一个很好的选择。原生 crypto 模块的兼容性仍然存在着一定的问题，它并不能保证在 Node.js、浏览器等JavaScript运行环境中和 Crypto-JS 做的一样好。我想，应该是，“It is time to fork it.” —— 至少在原生 crypto 的所有 API 都得到广泛支持之前。
The documentation said, 'It is time to go for the native crypto module,' but I don't believe using the native crypto module is currently the best choice. There are still compatibility issues with the native crypto module, and it cannot guarantee the same level of performance across JavaScript runtime environments like Node.js and browsers as Crypto-JS does. I think it should be more like, 'It is time to fork it.' — at least until all APIs of the native crypto module receive widespread support.