This is probably a good thing in the long run. Timer-based callbacks can generally be replaced by events, which only trigger when there is actually work to be d

This is probably a good thing in the long run. Timer-based callbacks can generally be replaced by events, which only trigger when there is actually work to be done. Many JS timers I've seen are needlessly busy-polling. Whether this implementation affects just timer callbacks or all background processing (eg websocket data events) is a bit ambiguous - this blog post seems to suggest major apps like Slack and Discord will break, but surely they are using websockets and not continuously polling for new data.