3 ms·
> Though not a part of this specification, we intend for the role of "threads" to be played by Web Workers in web browser environments.
by chrisseaton 11y ago
> Though not a part of this specification, we intend for the role of "threads" to be played by Web Workers in web browser environments.
- TeMPOraL 11y agoWhich reminds me - and sorry for going slightly off-topic - why on Earth does the JS world invent so many new names for things that already have perfectly good ones? For instance, why "Web Workers" instead of "threads"?
- chrisseaton 11y agoBecause with threads you expect shared memory. Web workers currently communicate only by message passing, more like a basic UNIX process. But they're unlike a UNIX process in other ways. If they used an existing name someone else would be on here complaining about that.