3 ms·
> In our case, we still felt this decision was justified because we don't have to recreate a scheduler with all the complexity of React's; we can build a small,
by apprewired 4y ago
> In our case, we still felt this decision was justified because we don't have to recreate a scheduler with all the complexity of React's; we can build a small, self-contained implementation that only implements what we need.
I wish there were more details about this. Implementing a small scheduler seems like a monumental task and I'd love to learn more about how to implement a base-case.
- timfsu 4y agoNot OP, but if you're building a small scheduler for batching changes, it should be pretty straightforward: - `jobs` is an array of functions - enqueue adds a job to `jobs` and starts running jobs if not running - job running can be triggered by animation frames or setTimeout