{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/help/issues/560","repository_url":"https://api.github.com/repos/nodejs/help","labels_url":"https://api.github.com/repos/nodejs/help/issues/560/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/help/issues/560/comments","events_url":"https://api.github.com/repos/nodejs/help/issues/560/events","html_url":"https://github.com/nodejs/help/issues/560","id":219223315,"number":560,"title":"Does NodeJS have any plans for shared memory?","user":{"login":"hitsthings","id":631812,"avatar_url":"https://avatars2.githubusercontent.com/u/631812?v=3","gravatar_id":"","url":"https://api.github.com/users/hitsthings","html_url":"https://github.com/hitsthings","followers_url":"https://api.github.com/users/hitsthings/followers","following_url":"https://api.github.com/users/hitsthings/following{/other_user}","gists_url":"https://api.github.com/users/hitsthings/gists{/gist_id}","starred_url":"https://api.github.com/users/hitsthings/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hitsthings/subscriptions","organizations_url":"https://api.github.com/users/hitsthings/orgs","repos_url":"https://api.github.com/users/hitsthings/repos","events_url":"https://api.github.com/users/hitsthings/events{/privacy}","received_events_url":"https://api.github.com/users/hitsthings/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2017-04-04T11:44:15Z","updated_at":"2017-05-25T12:12:27Z","closed_at":"2017-04-04T11:58:08Z","body":"So [this API](https://github.com/tc39/ecmascript_sharedmem) is being added to JS that allows different execution contexts to share a chunk of memory safely with interleaved access.\r\nMeanwhile the Web Worker spec already exists for creating these separate execution contexts.\r\n\r\nI know there are pre-existing user space modules for web-worker implementations. But they either 1) use separate processes for each thread (and thus can't really share memory well), or 2) they literally expose all memory to all threads and thus accept all the chaos that other multithreaded languages often have.\r\n\r\nCombined, the Web Worker and Shared Memory APIs seem like a solid infrastructure to build multithreading on. There would be no bad interaction with old code since the old code would have to opt in to using the shared buffer (or a bad dev would have to pass a shared buffer to the old code and then write to it). Is there any plan for making use of shared memory and web workers in Node?"},"comment":{"url":"https://api.github.com/repos/nodejs/help/issues/comments/303995792","html_url":"https://github.com/nodejs/help/issues/560#issuecomment-303995792","issue_url":"https://api.github.com/repos/nodejs/help/issues/560","id":303995792,"user":{"login":"addaleax","id":899444,"avatar_url":"https://avatars1.githubusercontent.com/u/899444?v=3","gravatar_id":"","url":"https://api.github.com/users/addaleax","html_url":"https://github.com/addaleax","followers_url":"https://api.github.com/users/addaleax/followers","following_url":"https://api.github.com/users/addaleax/following{/other_user}","gists_url":"https://api.github.com/users/addaleax/gists{/gist_id}","starred_url":"https://api.github.com/users/addaleax/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/addaleax/subscriptions","organizations_url":"https://api.github.com/users/addaleax/orgs","repos_url":"https://api.github.com/users/addaleax/repos","events_url":"https://api.github.com/users/addaleax/events{/privacy}","received_events_url":"https://api.github.com/users/addaleax/received_events","type":"User","site_admin":false},"created_at":"2017-05-25T12:12:27Z","updated_at":"2017-05-25T12:12:27Z","body":"@icodeforlove Hey, just so you are aware: https://github.com/nodejs/node/issues/13143, https://github.com/nodejs/worker. :)"}}
{"actor":{"display_login":"addaleax"}}