threadbox VS discordeno

Also, I find the JavaScript single threaded / async execution model far more attune to real work. In C# you would require a synchronization context to yield async work back to the host thread to run sync, but JavaScript makes this a default (i.e. event loop). Also the Web Worker, Shared Array Buffer and Atomics provide a far more approachable threading model, so if no memory is shared, then there's no need to lock, but if you do need to lock, it's opt in and apparent. It's also why I wrote this

I have been planning on writing a Deno version of https://github.com/sinclairzx81/threadbox once Deno worker thread and Shared Array Buffer gets better. It may be possible to implement CAS in user lib space.

I feel your pain with respect to working with worker_thread in Node. Not to lib drop, but this library might something you may be interested in https://github.com/sinclairzx81/threadbox

Non-Decorator JavaScript version https://github.com/sinclairzx81/threadbox/blob/master/doc/example.js

Actually, keen to get your thoughts on https://github.com/sinclairzx81/threadbox. worker_threads often get overlooked in the node sphere. Interested to hear what others who have looked at this feature think of this lib.

It's not, it only implemented the features I needed. You'd be better off looking at something more established like https://github.com/discordeno/discordeno :)