Zero-copy operations on the web

Open
#18 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
documentation

Research direction

Start with the explainer and the linked zero-copy slides at https://www.w3.org/2020/Talks/TPAC/unconference/zerocopy.pdf. Review the referenced threads near the end of the slides and document how zero-copy could help each relevant web use case. Done means the explainer covers those cases with clear, specific benefits.

Written by the indexing model from the issue text.

Description

A couple of years ago @tidoust and @dontcallmedom hosted a session on zero-copy for which the slides are available here: https://www.w3.org/2020/Talks/TPAC/unconference/zerocopy.pdf

Near the end there's a number of threads referenced of where the web might benefit from zero-copy. I think it would benefit the explainer if it detailed how it would help in those cases.

cc @padenot

Dominant language
JavaScript
Stars
38
Forks
7
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tc39/proposal-immutable-arraybuffer

All issues in tc39/proposal-immutable-arraybuffer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.