You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have no feature requests, it's basically perfect as-is.
Using this as a way to put all of my UDP + networking work into a separate thread and provide a pollable, lockless, GC-less interface to that from the main thread. As long as the 2 threads are able to keep up with each other and not overflow the SABs this works phomenally well.
Thanks so much for this no-bullshit, just enough abstraction to make Atomics usable interface!
The text was updated successfully, but these errors were encountered:
You'll be pleased to know that just by opening an issue here, you reminded me that I completely forgot to review + merge #29, that brings a million improvements, including typescript types, while being completely drop-in replacement: no API change except adding some method variants because there were some inconsistencies, and improving the performance significantly (more or less 2x throughput, depending on the browser).
Expect a new tagged version soon on npm that you should just be able to pull in without touching your own code, to have better performance (or copy the .js file manually, etc., like it's possible to do today).
I have no feature requests, it's basically perfect as-is.
Using this as a way to put all of my UDP + networking work into a separate thread and provide a pollable, lockless, GC-less interface to that from the main thread. As long as the 2 threads are able to keep up with each other and not overflow the SABs this works phomenally well.
Thanks so much for this no-bullshit, just enough abstraction to make
Atomics
usable interface!The text was updated successfully, but these errors were encountered: