Per #6, it seems super easy and applicable to port functionality to expressJS and hide this behind an API. This isn't ideal for those who need super^super performance, but super useful for those adding into a home library setup.
Assuming we can keep computation under 10-30ms, this should actually be fine. I've been testing with variable network latency (1-15ms) and not seeing a large effect. The color propagation will be a little bit more behind, maybe racy, but this is a very important use case in my opinion.
I'm going to tag this as a "new comer" bug for now. In my head, I'm thinking we might want this in a new library to separate out concerns. If you want to jump in, fork this library and build it. We'll consider merging it down the road if needed.
--Jake
Per #6, it seems super easy and applicable to port functionality to expressJS and hide this behind an API. This isn't ideal for those who need super^super performance, but super useful for those adding into a home library setup.
Assuming we can keep computation under 10-30ms, this should actually be fine. I've been testing with variable network latency (1-15ms) and not seeing a large effect. The color propagation will be a little bit more behind, maybe racy, but this is a very important use case in my opinion.
I'm going to tag this as a "new comer" bug for now. In my head, I'm thinking we might want this in a new library to separate out concerns. If you want to jump in, fork this library and build it. We'll consider merging it down the road if needed.
--Jake