warning: Creating default object from empty value in /home/buckman/public_html/neo/modules/taxonomy/ on line 33.
Mark Vergeer's picture

Chrome stops supporting third party plug-ins

ChromeChrome Google is joining together their YouTube and the Google+ platforms, whether users like it or not, but also has something else up its sleeve. By January, Google strives to have complete control over Chrome extensions and will turn off support for all third party extensions that are not downloaded from the Chrome Web Store. This all to supposedly make the browser a safer one.

Downloading Chrome extensions outside of Google's Web store will be prohibited come January. Until then, it is possible to download and manually install third party extensions on the Windows version of the popular Google browser. You can still do so by dragging the extensions to the Chrome://Extensions/ folder.

With this action, Google will gain complete control over their Web browser. Only Google will be able to decide which extensions will and will not be included in the store. A sign of things to come is the fact that earlier this year Google already removed ' Adblock' and ' Adaway' from the Google Play Store. And in January this will be a reality on Windows too.

Developers who want to publish an extension for the Windows Chrome version will have to pay a 5 dollar registration fee, and Google will take 5% off any revenues...

Bill Loguidice's picture

Thoughts on Google's Big Reveals

Hot on the heels of yesterday's striking Vizio Co-Star announcement - a proper Google TV device for $99 that also happens to incorporate the excellent OnLive streaming game service - was Google's big I/O event today. There were several major reveals, including the nifty features of the next version of the Android operating system, Jellybean; the Nexus 7 7" tablet; the Google Nexus Q, a streaming media device that's made in the USA; and Project Glass, Google's upcoming augmented reality glasses. Let's take each one of these in order:

Bill Loguidice's picture

Made the Switch from Firefox to Chrome

I finally tired of the memory leaks in Firefox and switched to Chrome. While I love the look/feel/interface of Firefox, enough was enough, as I'm a heavy extension user and like to leave a minimum of four or five tabs open at any one time. While Firefox now has a nice cross system sync for things like bookmarks and passwords (I dropped XMarks when they were debating about going out of business; they did recently get new funding), it also pales in comparison to Chrome's cross system sync, which sync's EVERYTHING in the browser, including all of your extensions and settings. What I miss in Chrome is the Google Toolbar (ironically) and the search box in the upper right of Firefox, where I would often search Amazon, Wikipedia and YouTube directly. There is no equivalent in Chrome as Google wants you to use the URL window as your search bar, which sadly allows for only one default search engine (in this case, I use Google), creating a multi-step process or requiring a different type of keyword searching.

A clean open of Firefox can start out anywhere. For instance, a clean open of Firefox just now started out 103MB on the iGoogle page, which is my default. Not touching it, it stabilized just under 102MB. A clean open of Chrome on the same system started out at 63MB. Opening up two Websites, Chrome shot up to 72MB. Firefox in that same time - again, not doing anything - shot up to 113MB. I then opened up two of the same exact pages as in Chrome and peaked at 142MB before settling down to 136MB. Now I can see Firefox leaking memory and shooting up to 185MB. Chrome is now up to 73MB. Firefox now just jumped up to 204MB, while Chrome remains at 73MB and occasionally as low as 71MB. So yeah, a serious issue with Firefox (and as type this, it's now up to 205MB) all in the span of a few minutes...

Syndicate content