Web Workers are useless. What we need is Web pthreads. Multithreading and shared state are messy, and it's fruitless to pretend otherwise.
-
-
Replying to @TimSweeneyEpic
@TimSweeneyEpic@Khakionion You don't understand the web. Go work on a browser team for a few years then come back with an informed opinion1 reply 0 retweets 0 likes -
Replying to @greggman
@greggman@Khakionion I don't care about the web. I just wanr a practical C++ compilation target. JavaScript is my assembly language.2 replies 0 retweets 4 likes -
Replying to @TimSweeneyEpic
@TimSweeneyEpic@Khakionion Your chances of getting Moz, Apple, & MS to adopt native client are far higher than JS getting multi-threading1 reply 0 retweets 0 likes -
Replying to @greggman
@greggman@TimSweeneyEpic@Khakionion I don't think so:https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/d-0ibJwCS24 …1 reply 0 retweets 1 like -
Replying to @aras_p
@aras_p@TimSweeneyEpic@Khakionion that's not pthreads AFAIK. You still can't call any apis from workers which is what native client solved4 replies 0 retweets 0 likes
@greggman @aras_p @Khakionion Shared asm.js state, locks, and a thread-safe API subset are essential to the web as a viable platform.
-
-
Replying to @TimSweeneyEpic
@TimSweeneyEpic@aras_p@Khakionion yes, native client did that. Other browser vendors said "too much work to make thread safe apis so no"0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.