Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta: Update Explainer for Isolated Realms #292

Merged
merged 11 commits into from
Apr 12, 2021
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,7 @@ See some examples [in the Explainer file](explainer.md).

## <a name='History'></a>History

* we moved on from the exposed globalThis model to a lean isolated realms API (see #289 and #291)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isolated realms => Realm with Callable Boundary or something like that...

we chatted about this with Shu, and I believe we should avoid using the term isolated realm all together.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another alternative is also "Callable Realms"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find the names that @caridy is suggesting confusing, though avoiding the word "isolated" could be useful to avoid other kinds of confusion. Maybe we could avoid giving this version a name for now, until we're really confident in one, since it's awkward to change names later.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* we moved on from the exposed globalThis model to a lean isolated realms API (see #289 and #291)
* we moved on from the exposed globalThis model to a revisited format of Realms with a Callable Boundary API (see #289 and #291)

How about this? We can't explain what this is in a single line, but we can further explain the function auto wrapping creates this callable boundary.

* we worked on this during ES2015 time frame, so never went through stages process ([ES6 Realm Objects proto-spec.pdf](https://github.com/tc39/proposal-realms/files/717415/ES6.Realm.Objects.proto-spec.pdf))
* got punted to later (rightly so!)
* goal of this proposal: resume work on this, reassert committee interest via advancing to stage 2
Expand Down
Loading