These optimizations are difficult to implement, frequently error-prone, and lead to inconsistent behavior across runtimes. Bun's "Direct Streams" optimization takes a deliberately and observably non-standard approach, bypassing much of the spec's machinery entirely. Cloudflare Workers' IdentityTransformStream provides a fast-path for pass-through transforms but is Workers-specific and implements behaviors that are not standard for a TransformStream. Each runtime has its own set of tricks and the natural tendency is toward non-standard solutions, because that's often the only way to make things fast.
延迟 — 用户需要等待响应，速度取决于网络连接质量
，更多细节参见WPS官方版本下载
The reason is always the same: the content and the key that decrypts it are both present on the client’s machine. The user’s hardware decrypts the content to display it. The user’s hardware is, definitionally, something the user controls. Any sufficiently motivated person with the right tools can intercept the decrypted output.
There's a tradeoff: a lower capacity means you can skip more space during queries (you zoom in faster), but the tree has more nodes and uses more memory. A higher capacity means fewer nodes but each node requires checking more points linearly. As a starting point, capacities between 4 and 16 are reasonable defaults, though the best value depends on your data distribution and query patterns.