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

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=174276

Asmithdev <austin at asmithdev.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |austin at asmithdev.com

--- Comment #5 from Asmithdev <austin at asmithdev.com> ---
I have read through this proposal throughly and I feel it is important to voice my concerns as I feel I am fairly qualified to speak on the subject. 

Additionally I would have appreciated if the author of this proposal would have made references to existing work that already allows not only concurrent but true parallel execution of javascript logic, **without** having to modify the underlying execution system.

Atomic operations are not a new thing and I have waited a significant portion of time for them to become mainstream and I have invested the last 3 years of my free time developing and improving my own library Hamsters.js which includes a fully featured thread pool with a proper queue system as well and makes use of the existing WebWorker spec to accomplish this. 

The performance limitations I face in the library today revolve entirely around the lack of main stream support for Atomic Operations, the proposed API seems like an attempt to basically negate the massive amount of effort that has gone into making practical use of the existing WebWorker specification for true concurrent and parallel execution of JavaScript logic. Should this proposal ever come to fruition I fear that not only will it cause a rift in the JavaScript community but it will also cause a huge problem for people like myself who have invested years and countless resources into supporting this functionality using EXISTING language conventions and specs.

I find it somewhat unprofessional that such a lengthy article was written up that never referenced work that already brought this functionality to the language and doesn't require throwing the underlying nature of the language out of the window.

Lastly I think work should be prioritized on finishing Atomic Operations support and making it mainstream so I don't have to deal with passing data around like I do now.

-- 
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/20170901/a3236db4/attachment.html>