Linked by Thom Holwerda on Thu 11th Dec 2008 22:18 UTC
Google After just 100 days, Google has lifted the veil of betaness off its web browser, Chrome, by releasing version 1.0. When Chrome made its first public appearance earlier this year, it was met with positive reveiws due to its JavaScript performance, as well as its robust multithreaded model. Now that the beta label has been ripped off Chrome, Google can't hide itself anymore: Chrome will now have to take Firefox and Internet Explorer head-on.
Thread beginning with comment 340259
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by Thom_Holwerda
by google_ninja on Sun 14th Dec 2008 05:50 UTC in reply to "RE: Comment by Thom_Holwerda"
google_ninja
Member since:
2006-02-05

why? the web is too dynamic, so you want to downgrade your experience?

that plugin always confused me. what next, a plugin to disable css?

Reply Parent Score: 2

mightshade Member since:
2008-11-20

Nah, on the sites regularly used, scripts are usually fine. They can still be enabled on demand and per site (as opposed to enabling/disabling scripts from the menu for the whole browser).

However, they aren't always used for enhancing a website. E.g. since browsers started blocking popups, ad developers worked around that using those annoying div-layer ads. Most of these don't shop up with scripts disabled.
Another example are embedded, automatically loading music players. I listen to my own music already, thank you very much.

As for "NoCSS", I'd actually like to block background transparency. ;) On my machine, it makes scrolling choppy at best, and most times it doesn't really look that good anyway.

Edited 2008-12-16 01:33 UTC

Reply Parent Score: 1