[kevin_thibedeau]

You can control how much is "spent" with with a cap on CPU utilization.

[perl4ever]

I'm not sure if that would slow the page down and make it unusable though. Prioritizing non-mining activity seems like it might be trickier than simply capping processor usage.

Although it's not quite the same thing, it makes me think of how bandwidth heavy pages are now. Once upon a time, I browsed the web on 56K, or even 14.4K. Now, when my phone gets throttled to 128K many sites are unbearable.

[castle-bravo]

My phone is currently throttled to 8kB/s. The only thing I can read is Hackernews; this is a well-built site.

[kristianp]

Reminds me of google web lite. Its used on slow mobile connections from google search in some countries. https://support.google.com/webmasters/answer/6211428?hl=en

[Fej]

CNN Lite comes to mind.

https://lite.cnn.io/en

[AstralStorm]

Browsers do not provide such caps for JS CPU usage. Maybe they should.

This is extra bad when you're viewing on a phone, tablet or battery powered laptop.

[majewsky]

If this problem persists, we will see tools popping up that use the OS APIs for restricting resource usage (e.g. cgroups on Linux) when starting the browser.

[squarefoot]

All it needs is faking the available computing power to any process created by the browser, or run it into a VM with extremely limited resources.