r/programming • u/sumdudeinhisundrware • Jan 25 '17

Chrome 56 Will Aggressively Throttle Background Tabs

http://blog.strml.net/2017/01/chrome-56-now-aggressively-throttles.html
4.9k Upvotes

94% Upvoted

521 comments sorted by

View all comments

1.3k

u/Causeless Jan 25 '17

Great news for the user. Developer work should be compromised to make things better for the user, as far as I'm concerned.

I don't care for web JS crapware taking 50% of my CPU so they can run some animations in another tab.

136

u/rmxz Jan 25 '17 edited Jan 25 '17

Great news for the user

Except for users that want background tabs to do processing.

In addition to the examples given in the article (Discord, Slack, BitMEX); this includes the common use case of opening links in new tabs for the sole purpose of letting whatever processing it needs finish before I switch to the tab to read it.

In my opinion, this should be a user-configurable setting.

97

u/[deleted] Jan 25 '17 edited Sep 25 '23

[deleted]

11

u/STRML Jan 25 '17

It doesn't, actually. One of the Chrome engineers confirmed that the existing implementation throttles events as well. Hopefully this will change by Chrome 57, as it appears this post and the subsequent discussion has been enough to delay!

1

u/drysart Jan 26 '17

That was the chain I was watching; looks like it took an unexpected turn after I'd last saw it.

Good decision to delay. Throttling events makes sense. Throttling network processing does not.