[webkit-dev] Parallel JavaScript: Why a separate ParallelArray types

Joe Mason jmason at blackberry.com
Mon Apr 15 21:11:44 PDT 2013

> From: webkit-dev-bounces at lists.webkit.org [webkit-dev-bounces at lists.webkit.org] on behalf of Maciej Stachowiak [mjs at apple.com]
> Sent: Monday, April 15, 2013 10:05 PM
> To: Filip Pizlo
> Cc: Benjamin Poulain; webkit-dev at lists.webkit.org; dpranke at chromium.org
> Subject: Re: [webkit-dev] Parallel JavaScript: Why a separate ParallelArray types
> These languages are popular, but I believe most complex projects using them with threading a long tail of nasty 
> but hard-to-diagnose threadsafety bugs.

Indeed, my assumption was always that languages with special-purpose concurrency constructs were not popular for the same reason all special-purpose languages are not popular compared to C++: they're not C++. It's hard to get over the hump of competing with C++, and a new concurrency paradigm isn't enough to do it even if that paradigm is better than shared memory+mutexes. The lack of success isn't evidence that the concurrency construct is worthless, just that lacks whatever spark (which is often marketing and not technical superiority) that causes some languages to succeed and others to fail.


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

More information about the webkit-dev mailing list