# (Champion needed) Improve handling of network data

**URL:** <https://es.discourse.group/t/champion-needed-improve-handling-of-network-data/2529>\
**Category:** 🦋 Proposals\
**Tags:** proposal\
**Created:** [March 31, 2026, 1:52pm UTC](https://es.discourse.group/t/champion-needed-improve-handling-of-network-data/2529 "2026-03-31T13:52:38Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![markm](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/markm/32/19_2.png) [@markm](https://es.discourse.group/u/markm)\
**Post date:** [April 13, 2026, 12:04am UTC](https://es.discourse.group/t/champion-needed-improve-handling-of-network-data/2529/15 "2026-04-13T00:04:40Z")

</div>

You could avoid all the complexity issues of TOCTOU, detaching, transfer, etc by limiting the JSON feature to [GitHub - tc39/proposal-immutable-arraybuffer: A TC39 proposal for immutable ArrayBuffers · GitHub](https://github.com/tc39/proposal-immutable-arraybuffer) or Uint8Arrays on them.

Further, if engines supported a string-decode of an Immutable ArrayBuffer as a view onto the Immutable ArrayBuffer, the performance gain you seek could even happen without any new APIs or any API changes. OTOH, engines are unlikely to provide that string-as-view optimization.

---

_[View the full topic](https://es.discourse.group/t/champion-needed-improve-handling-of-network-data/2529)._