Re:Making a case for JavaScript, in-browser Mining
by philipodonnell on Thursday February 15, 2018 @09:47AM
(#16384370)
I mean its not like webpages know when tabs aren't active so they can suspend mining when you're not actively reading the content, right?
And its definitely not true that browsers can actively manage the resources available to inactive tabs, right?
Just because the current set of options doesn't respect these, that is not a reason to discard the idea entirely.
Re:Making a case for JavaScript, in-browser Mining
by Tade0 on Thursday February 15, 2018 @08:35AM
(#16383842)
Currently browsers assign less CPU time to tabs that are open but not in focus, so any mining would probably be affected as well.
In e.g. Chrome timer events in such a tab are fired only once per second.
Re:Making a case for JavaScript, in-browser Mining
by tjoff on Thursday February 15, 2018 @08:40AM
(#16383869)
Not good enough, not by a long shot. Even with that feature and all browser windows are completely minimized they still take a significant amount of CPU without any mining going on.
I don’t think it is. People open links in new tabs for later, and “later” can be quite a while.