The spec does not mandate buffer limits for tee(). And to be fair, the spec allows implementations to implement the actual internal mechanisms for tee()and other APIs in any way they see fit so long as the observable normative requirements of the specification are met. But if an implementation chooses to implement tee() in the specific way described by the streams specification, then tee() will come with a built-in memory management issue that is difficult to work around.
2026年中央一号文件提出“发展‘小而美’文旅业态”，明确了乡村游的发展方向。曾经，受困于同质化，乡村游千村一面。究其原因，是重投入、轻运营，重模仿、轻创新，一味追求“大而全”。这不仅忽视了乡村独特价值，还造成资源浪费。相反，“小而美”追求的是轻量化、精品化、特色化，以小投入撬动高效益，这符合产业发展规律，契合文旅消费趋势，贴合乡村实际情况，能有力推动乡村游长远发展。
，详情可参考WPS官方版本下载
Here's the equivalent with the new API:
▲地址：https://x.com/KingBootoshi/status/2027138938335637914