[Webkit-unassigned] [Bug 174276] JSC should support threads in JS

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Aug 31 06:11:52 PDT 2017


kungfusheep at gmail.com changed:

           What    |Removed                     |Added
                 CC|                            |kungfusheep at gmail.com

--- Comment #3 from kungfusheep at gmail.com ---
(In reply to Asbjørn Ulsberg from comment #1)
> While I'm not opposed to the idea of concurrency in JavaScript, I think the
> proposed API is archaic and quite frankly; horrible. It looks like the
> proposed API is heavily influenced by Java and while java.lang.Thread worked
> okay when it was devised over 20 years ago, it is hardly the best take on
> concurrency in 2017.
> Instead of basing JavaScript's concurrency model on Java's old API with
> explicit Thread objects, lock objects and complicated signalling mechanisms,
> a modern look on concurrency would be something more akin to Rust's with
> object ownership and implicit concurrency built in.
> Please take this as a praise of the idea of concurrency in JavaScript, but
> also a nudge to review the concrete API proposal and base it on a more
> modern take on concurrency than java.lang.Thread.

>From the recent post on the webkit blog...

"Our strawman proposal for concurrent JS is to simply add threads. Threads gets separate stacks but share everything else. Threads are great for our experiment because they are so general. We can imagine implementing many other kinds of concurrent programming models on top of threads. Thus, if we can get our VM to support threads, then we can probably get it to support lots of other concurrent and parallel programming models."

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170831/ac4ee828/attachment.html>

More information about the webkit-unassigned mailing list