Skip to content

Control, Safety, Performance? #421

@brandon942

Description

@brandon942

It creates a new copy of the built-ins from ECMAScript.

Does this proposal not take away control from the host (website owner) over what 3rd party scripts do?
Sharing the same context is very much desirable in almost all cases. Scripts "stepping on each other's feet" has not been an issue to my knowledge.
By wrapping APIs the host has visibility and control over which APIs are used and how they are used by subsequent scripts.
This proposal takes this control away and enables 3rd party scripts to hide and protect potentially undesired or malicious activity from the host.
I don't see how anyone but malicious actors benefit from this proposal.

Another issue is performance. If all frameworks see themselves encouraged to start using their own realm which comes at a memory and performance cost instead of sharing a global one then it will downgrade the performance of all websites.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions