Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome.userScripts API requires developer mode

developer.chrome.com

Post reply on HN
Print view View original

11–20 of 26 posts

Re: Chrome.userScripts API requires developer mode

#11

Post by gruez »

weikju wrote: post #9
zlg_codes wrote: post #3

Shame, Google keeps alienating me further from their software. There isn't a single business on this planet qualified to tell me how my computing should be. If I want Hannah Montana GIFs on every form element then damnit I should have the ability to do it. Any browser that gets between me and control over what comes over the wire, or the filesystem, is obsolete and user hostile.

> Shame, Google keeps alienating me further from their software. 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 flip side of this is that if you threaten to bail every time there's a "user-hostile move", you'll quickly run out of software/products to use. A few years ago there were users complaining about firefox being "user-hostile" because of [mr robot promo/pocket/addon signing/whatever], but if you bailed on firefox because those what are you going to use?

Re: Chrome.userScripts API requires developer mode

#13

Post by bugfix »

porridgeraisin wrote: post #7
mkl wrote: post #4

Currently I maintain a user script for myself and about 10 much-less-technical colleagues, which they install with Violent Monkey. With this change the ones who use Chrome will need to enable extension developer mode. Are there consequences to that, or is it just an extra step?

Just an extra step, it's a single toggle in about:extensions. Bonus: it let's them use extensions on their filesystem instead of only the chrome webstore.

It's a single step for now...

Re: Chrome.userScripts API requires developer mode

#14

Post by zlg_codes »

weikju wrote: post #9
zlg_codes wrote: post #3

Shame, Google keeps alienating me further from their software. There isn't a single business on this planet qualified to tell me how my computing should be. If I want Hannah Montana GIFs on every form element then damnit I should have the ability to do it. Any browser that gets between me and control over what comes over the wire, or the filesystem, is obsolete and user hostile.

> Shame, Google keeps alienating me further from their software. 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...

I already don't use them for my own stuff, and have recommended against them when asked. They're just ensuring that I start discounting anything of theirs without consideration or benefit of the doubt.

The doubt's run dry.

Re: Chrome.userScripts API requires developer mode

#16

Post by thomassmith65 »

gruez wrote: post #11
weikju wrote: post #9

Earlier quoted context omitted.

> Shame, Google keeps alienating me further from their software. 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 flip side of this is that if you threaten to bail every time there's a "user-hostile move", you'll quickly run out of software/products to use. A few years ago there were users complaining about firefox being "user-hostile" because of [mr robot promo/pocket/addon signing/whatever], but if you bailed on firefox because those what are you going to use?

In my case: Waterfox.

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.

Re: Chrome.userScripts API requires developer mode

#17

Post by devsda »

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...

Re: Chrome.userScripts API requires developer mode

#18

Post by no_time »

devsda wrote: post #17

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-blo…

This anti-user stance combined with WEI would have been the end of the web as we know it.

No doubt they will try again in 3 years.

Re: Chrome.userScripts API requires developer mode

#19

Post by legohead »

devsda wrote: post #17

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-blo…

Adblock browser vs non. adblock browser is a pretty easy and quick choice.

Re: Chrome.userScripts API requires developer mode

#20

Post by pjmlp »

zlg_codes wrote: post #3

Shame, Google keeps alienating me further from their software. There isn't a single business on this planet qualified to tell me how my computing should be. If I want Hannah Montana GIFs on every form element then damnit I should have the ability to do it. Any browser that gets between me and control over what comes over the wire, or the filesystem, is obsolete and user hostile.

Every user of Chrome or its skins, and every developer shipping Electron based applications has contributed to this state of affairs.
Post reply on HN