> Firstly, this isn't some weird ploy to boost ad revenue. Everything Google does is a ploy to boost ad revenue. That's the whole business model. > Without a

> Firstly, this isn't some weird ploy to boost ad revenue. Everything Google does is a ploy to boost ad revenue. That's the whole business model. > Without a doubt, it's being enforced for the first time due to some large account hijacking attack that has proven impossible to stop any other way. After so many years of bending over backwards to keep support for JS blocking users alive, it's presumably now become the weakest link in the digital Maginot line surrounding their network. You're doing two things here: 1. Reasoning from no evidence, and ignoring a much simpler reason in the process. 2. Acting like the honest web users, the ones blocking malware-laden JS, are the ones who are wrong. It's much simpler to conclude that Google engineers simply got lazy and decided to punt the hard work of security to some JS library, instead of looking at it honestly.