So far as the original message seemed to be saying, it isn't about the uBlock Origins of the world, well behaved, highly performant code. They don't hurt end u

So far as the original message seemed to be saying, it isn't about the uBlock Origins of the world, well behaved, highly performant code. They don't hurt end users. It's the badly written add-ons that they're trying to eliminate. Given what they're breaking by their chosen mechanism, I would have thought educating end users would be the better approach. The running Chrome instance would be able to tell that an add-on is a large source of blocking, and could easily pop up a warning to indicate such, complete with a one-click option to disable the add-on.