docs(readme): update docs

README.md

@@ -9,10 +9,15 @@
 
 **Mutative** - A JavaScript library for efficient immutable updates, 2-6x faster than naive handcrafted reducer, and more than 10x faster than Immer.
 
-Why are Mutative faster than spread operations(naive handcrafted reducer)?
+**Why is Mutative faster than the spread operation(naive handcrafted reducer)?**
+
+The spread operation has performance pitfalls, which can be detailed in the following article:
+
 - <a href="https://betterprogramming.pub/the-reduce-spread-anti-pattern-fc0c1c0b23f6" target="_blank">The Reduce ({…Spread}) Anti-Pattern</a>
 - <a href="https://jonlinnell.co.uk/articles/spread-operator-performance?fbclid=IwAR0mElQwz2aOxl8rcsqoYwkcQDlcXcwuyIsTmTAbmyzrarysS8-BC1lSY9k" target="_blank">How slow is the Spread operator in JavaScript?</a>
 
+And Mutative optimization focus on shallow copy optimization, more complete lazy drafts, finalization process optimization, and more.
+
 ---
 
 <details>
@@ -90,7 +95,7 @@ This is why Mutative was created.
 
 > Mutative passed all of Immer's test cases.
 
-Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.0 vs Immer v10.0.3]
+Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.3 vs Immer v10.0.3]
 
 ![Benchmark](benchmark.jpg)
 
@@ -508,10 +513,6 @@ expect(state.simpleObject).not.toBe(baseState.simpleObject);
 
 ## FAQs
 
-- Why does Mutative have such good performance?
-
-Mutative optimization focus on shallow copy optimization, more complete lazy drafts, finalization process optimization, and more.
-
 - I'm already using Immer, can I migrate smoothly to Mutative?
 
 Yes. Unless you have to be compatible with Internet Explorer, Mutative supports almost all of Immer features, and you can easily migrate from Immer to Mutative.

package.json

@@ -28,7 +28,7 @@
     "clean": "rimraf dist",
     "test:coverage": "jest --coverage && coveralls < coverage/lcov.info",
     "perf": "cd test/performance && NODE_ENV='production' ts-node add-data.ts && NODE_ENV='production' ts-node todo.ts && NODE_ENV='production' ts-node incremental.ts",
-    "benchmark": "yarn build && yarn benchmark:base && yarn benchmark:object && yarn benchmark:array",
+    "benchmark": "yarn build && yarn benchmark:base && yarn benchmark:object && yarn benchmark:array && yarn benchmark:class",
     "benchmark:base": "NODE_ENV='production' ts-node test/performance/benchmark.ts",
     "benchmark:object": "NODE_ENV='production' ts-node test/performance/benchmark-object.ts",
     "benchmark:array": "NODE_ENV='production' ts-node test/performance/benchmark-array.ts",

website/blog/releases/1.0/index.md

@@ -81,23 +81,23 @@ const state = create(baseState, (draft) => {
 
 > Mutative passed all of Immer's test cases.
 
-Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.0 vs Immer v10.0.3]
+Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.3 vs Immer v10.0.3]
 
 ![Benchmark](img/benchmark.jpg)
 
 ```
-Naive handcrafted reducer - No Freeze x 4,361 ops/sec ±0.99% (90 runs sampled)
-Mutative - No Freeze x 6,178 ops/sec ±1.41% (95 runs sampled)
-Immer - No Freeze x 5.79 ops/sec ±0.33% (19 runs sampled)
+Naive handcrafted reducer - No Freeze x 4,476 ops/sec ±0.38% (96 runs sampled)
+Mutative - No Freeze x 6,058 ops/sec ±0.91% (90 runs sampled)
+Immer - No Freeze x 5.80 ops/sec ±0.34% (19 runs sampled)
 
-Mutative - Freeze x 849 ops/sec ±0.19% (96 runs sampled)
-Immer - Freeze x 383 ops/sec ±0.77% (94 runs sampled)
+Mutative - Freeze x 971 ops/sec ±1.07% (98 runs sampled)
+Immer - Freeze x 380 ops/sec ±0.61% (94 runs sampled)
 
-Mutative - Patches and No Freeze x 764 ops/sec ±0.20% (96 runs sampled)
-Immer - Patches and No Freeze x 5.72 ops/sec ±0.34% (19 runs sampled)
+Mutative - Patches and No Freeze x 967 ops/sec ±0.94% (96 runs sampled)
+Immer - Patches and No Freeze x 5.83 ops/sec ±0.17% (19 runs sampled)
 
-Mutative - Patches and Freeze x 418 ops/sec ±1.23% (94 runs sampled)
-Immer - Patches and Freeze x 279 ops/sec ±0.54% (90 runs sampled)
+Mutative - Patches and Freeze x 502 ops/sec ±0.94% (96 runs sampled)
+Immer - Patches and Freeze x 278 ops/sec ±0.73% (90 runs sampled)
 
 The fastest method is Mutative - No Freeze
 ```
@@ -108,7 +108,7 @@ Run `yarn benchmark` to measure performance.
 
 Immer relies on auto-freeze to be enabled, if auto-freeze is disabled, Immer will have a huge performance drop and Mutative will have a huge performance lead, especially with large data structures it will have a performance lead of more than 50x.
 
-So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,178 ops/sec`) and Immer (`383 ops/sec`).
+So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,058 ops/sec`) and Immer (`380 ops/sec`).
 
 Overall, Mutative has a huge performance lead over Immer in [more performance testing scenarios](https://github.com/unadlib/mutative/tree/main/test/performance).
 

website/docs/extra-topics/comparison-with-immer.md

@@ -25,23 +25,23 @@ Mutative has fewer bugs such as accidental draft escapes than Immer, [view detai
 
 > Mutative passed all of Immer's test cases.
 
-Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.0 vs Immer v10.0.3]
+Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.3 vs Immer v10.0.3]
 
 ![Benchmark](img/benchmark.jpg)
 
 ```
-Naive handcrafted reducer - No Freeze x 4,361 ops/sec ±0.99% (90 runs sampled)
-Mutative - No Freeze x 6,178 ops/sec ±1.41% (95 runs sampled)
-Immer - No Freeze x 5.79 ops/sec ±0.33% (19 runs sampled)
+Naive handcrafted reducer - No Freeze x 4,476 ops/sec ±0.38% (96 runs sampled)
+Mutative - No Freeze x 6,058 ops/sec ±0.91% (90 runs sampled)
+Immer - No Freeze x 5.80 ops/sec ±0.34% (19 runs sampled)
 
-Mutative - Freeze x 849 ops/sec ±0.19% (96 runs sampled)
-Immer - Freeze x 383 ops/sec ±0.77% (94 runs sampled)
+Mutative - Freeze x 971 ops/sec ±1.07% (98 runs sampled)
+Immer - Freeze x 380 ops/sec ±0.61% (94 runs sampled)
 
-Mutative - Patches and No Freeze x 764 ops/sec ±0.20% (96 runs sampled)
-Immer - Patches and No Freeze x 5.72 ops/sec ±0.34% (19 runs sampled)
+Mutative - Patches and No Freeze x 967 ops/sec ±0.94% (96 runs sampled)
+Immer - Patches and No Freeze x 5.83 ops/sec ±0.17% (19 runs sampled)
 
-Mutative - Patches and Freeze x 418 ops/sec ±1.23% (94 runs sampled)
-Immer - Patches and Freeze x 279 ops/sec ±0.54% (90 runs sampled)
+Mutative - Patches and Freeze x 502 ops/sec ±0.94% (96 runs sampled)
+Immer - Patches and Freeze x 278 ops/sec ±0.73% (90 runs sampled)
 
 The fastest method is Mutative - No Freeze
 ```
@@ -52,7 +52,7 @@ Run `yarn benchmark` to measure performance.
 
 Immer relies on auto-freeze to be enabled, if auto-freeze is disabled, Immer will have a huge performance drop and Mutative will have a huge performance lead, especially with large data structures it will have a performance lead of more than 50x.
 
-So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,178 ops/sec`) and Immer (`383 ops/sec`).
+So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,058 ops/sec`) and Immer (`380 ops/sec`).
 
 Overall, Mutative has a huge performance lead over Immer in [more performance testing scenarios](https://github.com/unadlib/mutative/tree/main/test/performance). Run `yarn performance` to get all the performance results locally.
 

website/docs/getting-started/performance.md

@@ -69,23 +69,23 @@ const state = create(baseState, (draft) => {
 
 > Mutative passed all of Immer's test cases.
 
-Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.0 vs Immer v10.0.3]
+Measure(ops/sec) to update 50K arrays and 1K objects, bigger is better([view source](https://github.com/unadlib/mutative/blob/main/test/performance/benchmark.ts)). [Mutative v1.0.3 vs Immer v10.0.3]
 
 ![Benchmark](img/benchmark.jpg)
 
 ```
-Naive handcrafted reducer - No Freeze x 4,361 ops/sec ±0.99% (90 runs sampled)
-Mutative - No Freeze x 6,178 ops/sec ±1.41% (95 runs sampled)
-Immer - No Freeze x 5.79 ops/sec ±0.33% (19 runs sampled)
+Naive handcrafted reducer - No Freeze x 4,476 ops/sec ±0.38% (96 runs sampled)
+Mutative - No Freeze x 6,058 ops/sec ±0.91% (90 runs sampled)
+Immer - No Freeze x 5.80 ops/sec ±0.34% (19 runs sampled)
 
-Mutative - Freeze x 849 ops/sec ±0.19% (96 runs sampled)
-Immer - Freeze x 383 ops/sec ±0.77% (94 runs sampled)
+Mutative - Freeze x 971 ops/sec ±1.07% (98 runs sampled)
+Immer - Freeze x 380 ops/sec ±0.61% (94 runs sampled)
 
-Mutative - Patches and No Freeze x 764 ops/sec ±0.20% (96 runs sampled)
-Immer - Patches and No Freeze x 5.72 ops/sec ±0.34% (19 runs sampled)
+Mutative - Patches and No Freeze x 967 ops/sec ±0.94% (96 runs sampled)
+Immer - Patches and No Freeze x 5.83 ops/sec ±0.17% (19 runs sampled)
 
-Mutative - Patches and Freeze x 418 ops/sec ±1.23% (94 runs sampled)
-Immer - Patches and Freeze x 279 ops/sec ±0.54% (90 runs sampled)
+Mutative - Patches and Freeze x 502 ops/sec ±0.94% (96 runs sampled)
+Immer - Patches and Freeze x 278 ops/sec ±0.73% (90 runs sampled)
 
 The fastest method is Mutative - No Freeze
 ```
@@ -96,6 +96,6 @@ Run `yarn benchmark` to measure performance.
 
 Immer relies on auto-freeze to be enabled, if auto-freeze is disabled, Immer will have a huge performance drop and Mutative will have a huge performance lead, especially with large data structures it will have a performance lead of more than 50x.
 
-So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,178 ops/sec`) and Immer (`383 ops/sec`).
+So if you are using Immer, you will have to enable auto-freeze for performance. Mutative is disabled auto-freeze by default. With the default configuration of both, we can see the 16x performance gap between Mutative (`6,058 ops/sec`) and Immer (`380 ops/sec`).
 
 Overall, Mutative has a huge performance lead over Immer in [more performance testing scenarios](https://github.com/unadlib/mutative/tree/main/test/performance). Run `yarn performance` to get all the performance results locally.