I would like to say the industry is run by the people that create it. In practice, it is also run by people in the periphery. When I think of toxic devs I thin

I would like to say the industry is run by the people that create it. In practice, it is also run by people in the periphery. When I think of toxic devs I think of being dismissed when I talk about attention span and optimised page load speeds. And perhaps devs who feel that what is currently normal in javascript land (not knowing your stack, many dependencies, perhaps feeling like electron is an okay solution for a very simple problem) is acceptable because that's just how it's done right now. Both of those schools of thought have reasons for why they are so wide-spread, but they're wasteful and in my eyes an example of lazy engineering. That's acceptable as a conscious choice, but not as a default solution. I actually feel as if most of the designers understand efficiency better than the really problematic devs (especially as it relates to page load speed), but maybe I've met mostly really nice designers :) There's a lot of patching that could be done at the browser level and I think what you've proposed is a reasonable choice. The nice thing about timer throttling is that it's relatively easy to implement and nothing of value will be lost.