Very interesting, this is great to see an alternatives to queues with tasks, since that is what I mostly use in application code. I still would like a clear explanation on when I would use this vs. when to use a concurrent queue. What situations would the concurrent queue be clearly better, and which situations would the work contracts be clearly better? There's no way work contracts are better for every situation, even with future improvements.
kewl. i wonder how a tree with 4 children per node would compare, if there is any benefit in tree navigation compared to the tradeoff of more contention per node
I’m not quite following how scalability works if the usage pattern ends up biasing a single work contract (all requests are for the same type of work) as it seems benefits come from work of different work contracts being scheduled.
i want to give a hint: when you cannot read the code on the slides, neither can the audience. please put less code on the slides and make it bigger. (this applies to many presentations, not just you)
Thanks for the breakdown! Just a quick off-topic question: I have a SafePal wallet with USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). Could you explain how to move them to Binance?
Really great talk! Concise and comprehensive... I wish all talks were like this
This talk is excellent! Great work
Such a great talk
Very interesting, this is great to see an alternatives to queues with tasks, since that is what I mostly use in application code.
I still would like a clear explanation on when I would use this vs. when to use a concurrent queue. What situations would the concurrent queue be clearly better, and which situations would the work contracts be clearly better? There's no way work contracts are better for every situation, even with future improvements.
Thanks for the question. I added a section to the repo's README to provide answers. I hope that helps.
This is a great approach! I wonder about the cost of going through so many atomics though.
Thanks for the question. I added a section to the repo's README to provide answers. I hope that helps.
kewl. i wonder how a tree with 4 children per node would compare, if there is any benefit in tree navigation compared to the tradeoff of more contention per node
Thanks for the question. I added a section to the repo's README to provide answers. I hope that helps.
I’m not quite following how scalability works if the usage pattern ends up biasing a single work contract (all requests are for the same type of work) as it seems benefits come from work of different work contracts being scheduled.
Thanks for the question. I added a section to the repo's README to provide answers. I hope that helps.
"Could you imagine writing your code and queueing lines of code to be executes", bro has not done a lot in modern JS.
i want to give a hint: when you cannot read the code on the slides, neither can the audience. please put less code on the slides and make it bigger. (this applies to many presentations, not just you)
otherwise great presentation. very interesting technique. thanks ;)
Noted. I'll make the font larger in the future. 😀
Thanks for the breakdown! Just a quick off-topic question: I have a SafePal wallet with USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). Could you explain how to move them to Binance?