I didn't say that, and I would assume most HN readers understand I was moving from the specific concerns content blockers have with your 'WebBundles' proposal to commentary on the wider motivations of Google: that its business interests logically drive it to find ways to thwart content blockers which frustrate their ad-tech ecosystem.
A web architecture which does not allow content to be modified – one that results in websites being a 'black box' – is the ideal outcome for Google's ad-tech ecosystem.
I am hardly claiming any one initiative takes us straight there - that would be quite the poor strategic play from Google. But Google's changes to Chrome to frustrate content-blockers [1], through to AMP and now WebBundles paint a disturbing picture for independent observers.
For examples that might speak to the institutional strategies employed by Google, recall the claims from Johnathan Nightingale that Google systematically sabotaged Firefox over a decade [2].
Those claims are telling not just for the institutional analysis, but for the revelation of an honest mindset among Google engineers internally:
"I think our friends inside Google genuinely believed that. At the individual level, their engineers cared about most of the same things we did."
When I see the valid claims made of serious issues around AMP and WebBundles, and see honest, heartfelt responses from Google engineers that it's all fine and a beat-up, I can't help but think of Nightingale's observations.
"Hey everyone, it's all fine. We mean well. Don't worry - nothing to see here."
[1] https://www.cnet.com/news/google-holds-firm-on-chrome-change...
[2] https://www.zdnet.com/article/former-mozilla-exec-google-has...