Why Chrome has No NoScript
hackademix.net
hackademix.net
"The following lists some types of extensions that we'd like to eventually support:"
[...]
* "Content filtering: Adblock, Flashblock, Privacy control, Parental control"
Technical details: http://boredzo.org/blog/archives/2009-01-29/how-clicktoflash...
I'd love to see a similar plugin on Linux for Firefox, Chromium etc.
http://boredzo.org/blog/archives/2009-01-29/how-clicktoflash...
I know a lot of people that run AdBlock, but outside the hardcore techie crowd I know very few who run NoScript.
Anecdotal observation doesn't mean much, so numbers would be appreciated.
Also, NoScript requires a lot (relatively speaking, of course) of interactively applied knowledge about web technologies. I'm fairly certain the people who use it make up a very small segment of Google's target audience.
I'd expect the number who use NoScript to be 1-2% if that.
Note this is out of a mainly firefox userbase. For the general web those %'s would be far lower.
"Write some C++ code and spend two hours recompiling" is not a reasonable answer to "how do you modify the browser's UI?", especially for tasks that can be done in seconds without restarting in Mozilla.
Huh? So... If I like Chrome the way it is and don't want to turn my browser into Emacs, I 'lack the imagination to come up with a better UI?'
Instead, I suggest the weak bits of the claim are the omission - Chrome is also great for other people too - and the unjustified implication that being unable to come up with a better UI is a problem (it applies to most of us).
Google guy 1: we really have to figure how to prevent people from building noscript-alike extension.
Google guy 2: hey, I have an Idea! Let's ask the author what are the important API to do so in order to avoid the development of such APIs!
Google guy 1: you are a genius! I'm phoning him just now.
That's not what happened I guess.
http://hackademix.net/2009/12/10/why-chrome-has-no-noscript/...
That comment points to a Chromium tracking bug, here:
http://code.google.com/p/chromium/issues/detail?id=16932
It looks like while a developer at Google was working on this project, that developer left Google in October and there's been no replacement.
While this doesn't suggest the feature is the highest priority for Google, it also doesn't suggest Google is deliberately intending to prevent JavaScript or advertising blocking. Sometimes things that didn't get done just didn't get done.
To my last count they currently have 5 ad blocking extensions on Google extensions gallery. One of the is the second most downloaded Chrome Extension.
Generally speaking Google has done so much with Chrome browser in such a short time, I don't mind giving them the benefit of doubt that they didn't get around fixing or implementing the said bug/feature.
On one hand, I'm blocking some of their potential impressions for their lower margin, add-on, commodity product. On the other hand I'm making supply of their higher margin main product more scarce, more valuable. I'm not sure th net effect is too worrying.
Of course this is anecdote but maybe I'm not the only one.
I use Google a lot & I know that I want the ads. For everything else, it's easiest to blanket opt out. Many sites (particularly Israeli news sites which I read sometimes) have ads that bother me a lot.
And yes, I'm aware the misleading title is the blogger's work - no need to perpetuate it.