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

One thing to understand here is that Realms are generally intended to be a sort of metaprogramming construct, which would be used by frameworks and libraries to build emulated JS environments for developers. I understand the feedback that this concept may be difficult for JS developers to understand; probably an introduction in the explainer to show how mĂșltiple globals in JS already work would help make this document more accessible. Either way, it is an underlying primitive in the platform.

> Maybe for consistency sake it would make sense to have an accessor to expose it as a realm, thought currently the only thing exposed is globalThis and import - but we assume that could be extended in the future.

Trying to understand this comment--what would this accessor be? What does "it" refer to--are you suggesting making an accessor named `window`? Just to explain the design of this API, the idea is that everything in the global object hangs off of `globalThis`. I don't understand the function of adding synonyms; the API here seems learnable to me.

Does the TAG have any thoughts about https://github.com/tc39/proposal-realms/issues/238 ?

-- 
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#issuecomment-698834574

Received on Friday, 25 September 2020 09:45:52 UTC