Slashdot Mirror
Google Chrome Extensions Are Now Available
kai_hiwatari writes "The Google Chrome Extensions site is now open for Windows and Linux users — but not yet for Mac — and contains around 300 extensions. AdBlock is not yet available, however. (The closest thing to it is Adsweep, but right now it seems to be broken. Who wants to take this on?) Does the availability of extensions put Chrome at risk of becoming bloated, like many complain about with Firefox?"
I think the problem is all the extra javascript that is being added to the average web site. I've noticed sites getting slower and slower even on the same version of Firefox. Then 3.5 came out and sped things up a bit. I suspect that this will encourage developers to use more excessive javascript when it's not necessary and slow down their sites even more.
Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
I actually don't care if a site displays ads at me, so long as they're well-behaved.
But I don't want a site to do ANYTHING that moves unless I give it permission. NoScript handles that pretty well.
There is a Flashblock extension there, which is a good start, but I'm going to hold off switching to Chrome full-time until I can selectively disable Javascript. (There are many good uses of it as well, so I don't want it disabled entirely.)
Well, I've just dealt with Adblock in another post -- there are several adblocking extensions, and I wrote one myself in an afternoon. Trust me, adblock will happen, whether Google wants it or not.
So now let's talk about bloat...
First, I won't lie. It's a very real possibility. Take something like an adblocker -- in Chrome, that would be implemented as at least a "content script", a script which runs on every page. Every content script is adding some finite but real cost to the pages it effects. And of course, poor extension design would lead to a bloated browser.
On the other hand, no one's forcing you to install extensions, and a bare Chrome is much lighter than a bare Firefox.
Also, consider a properly designed extension -- you're going to have some of it running in the page as a content script, you might have some buttons in the toolbar, but chances are, you're also going to have a bunch of logic in a "background page", doing things like making HTTP requests, talking to your local sqlite database, messing with your bookmarks and tabs, and so on. A background page is essentially an HTML page that gets loaded in the background, and is completely invisible, except that scripts on it can talk to other parts of your extension. Add to that the fact that every popup, even configuration, is a separate HTML page, and communication between all of these happens through a message-passing API.
What does all of that mean?
It means that a fair chunk of every extension, including the glue that ties it together, is happening in a Background Page, which could very well be a separate process. I'm also fairly sure you can have more than one background page per extension. This means that almost by default, you have a certain amount of concurrency built in. So it might bloat, maybe, but it's certainly going to mean less chance for extensions to directly lag you, if they're all in a separate process -- possibly using a separate core.
Plus, v8 just screams.
Don't thank God, thank a doctor!
Chrome updates extensions in the background without prompts. I was actually surprised when I realized this had happened, didn't expect it.
the long term consequence of your point of view seems to be that all ad supported content will either disappear entirely or run to hide behind a paywall.
Right, and it will be replaced with content that doesn't require advertising to support it.
"Our two-party system is like a bowl of shit looking at itself in a mirror." - Lewis Black