Linked by Thom Holwerda on Thu 11th Dec 2008 22:18 UTC
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 340102
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-03-16
This is because the Firefox GUI is single-threaded. The plugin uses the same thread as Firefox and when it has a hard time loading the movie from youtube it hogs the thread.
Considering that Chrome wants to isolate everything to separate processes I guess they've done that with plugins as well, which means only the plugin gets stalled.
So to sum up: If you ever plan to do some heavy lifting, single threading things are not the way to go.