[w3ctag/design-reviews] Realms API ECMAScript Proposal (#542)

Saluton TAG!

I'm requesting a TAG review of __TC39's Realms API__.

Realms are a distinct global environment, with its own global object containing its own intrinsics and built-ins. The Realms proposal provides a new mechanism to execute JavaScript code within the context of a new global object and set of JavaScript built-ins. The Realm constructor creates this kind of a new global object.

  - Explainer¹ (minimally containing user needs and example code): https://github.com/tc39/proposal-realms/blob/main/explainer.md

  - Security and Privacy self-review²: WIP
  - GitHub repo (if you prefer feedback filed there): ttps://github.com/tc39/proposal-realms
  - Primary contacts (and their relationship to the specification):
      - Caridy Patiño (@caridy), co-champion, Salesforce
      - Mark S. Miller (@erights), co-champion, Agoric
      - Leo Balter (@leobalter), co-champion, Salesforce
      - Daniel Ehrenberg (@littledan), advisor, Igalia
  - Organization/project driving the design: Salesforce, Agoric
  - External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): none

Further details:

  - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/)
  - The group where the incubation/design work on this is being done (or is intended to be done in the future): TC39
  - The group where standardization of this work is intended to be done ("unknown" if not known): TC39
  - Existing major pieces of multi-stakeholder review or discussion of this design:
    - Presentations summarized [here](https://github.com/tc39/proposal-realms#presentations)
    - Lastest TC39 meeting notes about Realms [here](https://github.com/tc39/notes/blob/master/meetings/2020-06/june-4.md#realms-stage-2-update)
  - Major unresolved issues with or opposition to this design: https://github.com/tc39/proposal-realms/issues/238

  - This work is being funded by: Salesforce, Agoric

You should also know that...

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  - [x] 🐛 open issues in our GitHub repo for **each point of feedback**

  (_We are also fine to reuse this current issue_)

------------------------------------------------------------------------------------
CAREFULLY READ AND DELETE CONTENT BELOW THIS LINE BEFORE SUBMITTING

Please preview the issue and check that the links work before submitting.

In particular:
* if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document. We would prefer public documents though, since we work in the open.

¹ For background, see our [explanation of how to write a good explainer](https://w3ctag.github.io/explainers). We recommend the explainer to be in [Markdown](https://github.github.com/gfm/).

² Even for early-stage ideas, a Security and Privacy questionnaire helps us understand potential security and privacy issues and mitigations for your design, and can save us asking redundant questions. See https://www.w3.org/TR/security-privacy-questionnaire/.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/542