My issues with Chrome's handling of extensions
June 9, 2011
This got long enough that I've pulled it out of the original entry into a standalone entry.
(No, I don't have Google whitelisted for NoScript in Firefox. Yes, I'm peculiar.)
The second is that NotScripts does not have anywhere near as good an interface as NoScript does. I'm not sure if this is a Chrome limitation or just that NotScripts has not gone the extra distance, but it sort of feels like a Chrome issue to me; given their other behavior with extensions, I find it all too easy to believe that Chrome has deliberately limited what GUI interfaces are available to extensions and forced NotScript to jump through hoops to get even as much as it does now. When I'm using NotScripts, it's less clear what the state of things is on the current page, it's harder and takes me longer to do things, and I feel that the interface is not as clear.
* * *
Atom feeds are available; see the bottom of most pages.