limu VS mutative

limu is designed for modern browsers. It only considers the operating environment that supports Proxy and uses the mechanism of shallow copy on read and mark update on write. This allows users to operate variable data like original data. During the operation, only proxy objects are generated for the read nodes and returned to the user. After reading, the parent and child nodes are directly connected with shallow clone nodes. The proxy object is hidden in the meta data of the node. , after the operation is completed, a new data with structural sharing characteristics is generated, and the meta data generated during the reading process is removed.

for those recommending Immer, check out Mutative or Limu instead (much faster)

https://github.com/unadlib/mutative

https://github.com/tnfe/limu

Strongly recommend trying [limu](https://github.com/tnfe/limu)，it is now the fastest immutable data js lib，and it is also production environment available.

//You can verify through the following tests, and you are also welcome to add more performance test cases

Welcome to understand and pay attention to limu, visit documentation and right-click to bring up the console, you can ** Real-time experience **limu api and immer api for comparison (limu and immer objects are bound globally).

You are very welcome to submit your test to the benchmark directory of limu git repo

limu 🍋

The readme explains how Mutative achieves better performance over Immer: https://github.com/unadlib/mutative#readme

Efficient immutable updates, 2-6x faster than naive handcrafted reducer, and more than 10x faster than Immer.

High Performance Based on Mutative: Mutative is faster than the naive handcrafted reducer and 10x faster than Immer. Updates to immutable data based on Mutative also maintain good performance. The patches obtained from the shared state update are used for state synchronization.

for those recommending Immer, check out Mutative or Limu instead (much faster)

https://github.com/unadlib/mutative

https://github.com/tnfe/limu


At the same time, the number of single test cases has increased to 500+, with a coverage rate of '95+' (the results can be viewed by executing NPM run tests in the root directory)