Chrome.userScripts API requires developer mode(developer.chrome.com) |
Chrome.userScripts API requires developer mode(developer.chrome.com) |
From the chrome developer group[1]
> The devmode switch also enables other features e.g. chrome.declarativeNetRequest.onRuleMatchedDebug which may severely reduce the performance of the content blocking extensions, depending on how it's used.
Unless they are happy with degraded performance or needing to switch to developer mode often, users may have to chose between ad-blocking and custom scripts.
Chrome's current stance is that users have no right/legitimate business case running custom scripts on a site. You are allowed to do it only in the context of development. On the flip-side, this also means some features in development mode can potentially be restricted in the future saying they are non-essential for development.
Given all these hostile decisions, it is still our choice on whether we want to switch to a better browser or become the proverbial frog in the pot.
[1] https://groups.google.com/a/chromium.org/g/chromium-extensio...
As per [1], the chrome.declarativeNetRequest.onRuleMatchedDebug is available only for unpacked extensions i.e. local extensions with a specific permission. So, I'm not sure under what context there will be a performance impact.
Anyone more familiar with internals of chrome and/or extension development in general can clarify if there are any downsides to enabling dev mode permanently.
[1] https://developer.chrome.com/docs/extensions/reference/api/d...
I've seen no downsides myself.
Just going by the name, chrome.declarativeNetRequest.onRuleMatchedDebug, I'd expect that to be something that has to explicitly be used. Enabling developer mode would make it available which they say might reduce the performance "depending on how it's used", but would a production release of an ad-blocker extension be using it?
No doubt they will try again in 3 years.
Enabling developer mode will soon become mandatory for running userscripts via Tampermonkey.
Not a big deal for me, I have extension dev mode on all the time, but ymmv.
Some discussion here: https://groups.google.com/a/chromium.org/g/chromium-extensio...
Also, users can check one box in chrome settings in order to go around this. It’s a bit too easy to bypass IMO.
Tampermonkey: Dev Mode will become mandatory for running userscripts in Chromium - https://news.ycombinator.com/item?id=38533213 - Dec 2023 (75 comments)
Any browser that gets between me and control over what comes over the wire, or the filesystem, is obsolete and user hostile.
Then don't wait to jump ship, you know where things are going.. Otherwise you'll just get used to this latest round of user-hostile moves, then the next time you'll say the same thing after this is normalized.. and so on...
The doubt's run dry.
The statement "if you threaten to bail every time there's a user-hostile move, you'll quickly run out of software/products to use" seems true at first, but the longer one thinks about it, the less it makes sense.
If the argument is that all browsers have some user-hostile features, I disagree only meekly. If the argument is that all browsers are equally user-hostile, I disagree strongly.