| The requirement is not without side-effects. 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...