Realization striked me

Author: Guthib-of-Dan

README.md

@@ -43,6 +43,8 @@ When we receive a 1× payload and decode it we have 2× (UTF-8 if Latin chars) t
 
 The payload may be malformed, but to discover this we must incrementally parse it — the job of `JSON.parse`. We would rather skip the intermediate string entirely, identify problems early and protect the application under high load.
 
+Even if there is only one UTF-16 char in the string, it becomes twice as large in any case. If strings were parsed only one by one and inserted into the resulting structure, it would have MOST of the data UTF-8 and one 1 string UTF-16. This HUGELY improves performance of i18n services.
+
 ---
 
 Results of [Decoding benchmark](./demo/decoding.mjs) — 4 MB symbols, 100 iterations: