Computerworld has posted an article comparing Firefox’s 3.1 beta to the latest Chrome beta.
Steven J. Vaughan-Nichols put both of these browser through the SunSpider JavaScript benchmark test. Not surprising the results were very stunning with Firefox 3.1 beta taking it out.
Of interesting note is that Firefox 3.1 beta is almost 25 times faster when rendering JavaScript compared to Internet Explorer 7.
New Google Chrome builds are showing support for Greasemonkey, albeit very basic and still in early stages of development.
Until now, Greasemonkey has been a Mozilla Firefox extension that allows users to install scripts that make on-the-fly changes to most HTML-based web pages.
Martin from gHacks writes “Only scripts in c:\scripts are loaded and only if the user adds the parameter –enable-greasemonkey by appending it to the program’s shortcut.”
Support for Greasemonkey has been added as of build 3499, which can be downloaded from the Chromium build FTP.
Mashable has posted a great article with 25 resources on how to customise your favorite browser.
Included are resources for Internet Explorer, Firefox, Safari, Opera and Google Chrome.
You can read the full article on the Mashable website.
Happy customising!
With all the news that Google Chrome’s market share has droped since it’s release, I thought it was only fitting to add some more statistics to the fire.
On another technology site that I run, browser stats were as follows for the month of September:
Browser Market Share for September
Through the month of September, Chrome’s usage has dropped around 30% from its release. Usage seems to have stabalised since then.
Of interesting note, is that Google Chrome has still gained a larger market share than Opera. It should also be noted that Chrome is still only available on Windows. Perhaps it’s market share will again increase when offical Mac and Linux versions are released.
Perhaps Google Chrome hasn’t shaken up the market as much as everyone predicted. Did you try Google Chrome and are you still using it?
WebKit passing Acid3
The WebKit development team has just passed another huge milestone. The WebKit browser engine used in Apple’s Safari and Google’s Chrome now fully passes the Acid3 test.
The Acid3 test checks how well browsers comply with the latest standards, in particular JavaScript and the Document Object Model (DOM).
Maciej Stachowiak of the WebKit team attributes this feat to “recent speedups in JavaScript, DOM and rendering.”
Unfortunately, it will be a few months before we see this in Safari and Chrome, but while you wait you can download a nightly build of WebKit and test this for yourself.
Chromium on Linux
Thanks to the CrossOver Chromium project, it is now possible to download Google Chrome for Mac OS X and Linux.
The Chromium project is an open source effort, built using the same code as Chrome and “aims to build a safer, faster, and more stable way for all Internet users to experience the web“.
At this stage, the browser does not run nativly on systems other than Windows, but the Chromium project has been made possible thanks to the CodeWeavers’ Wine development expertise.
You can download the CrossOver Chromium browser from the website or the links below:
Mac OS X
Ubuntu and Debian (32bit)
Ubuntu and Debian (64bit)
Google Chrome Go Green Theme
In less than two weeks since Google Chrome was released, die-hard fans and users are already customising the browser. ChromeSpots Google Chrome Themes forum has plenty of themes to choose from already.
Theme’s resembling Apple’s Safari, to Mozilla’s Firefox, and even deviantART have all been created.
Once you download a theme you will need to install it. The install path is as follows:
Windows Vista
C:\Users\[user]\AppData\Local\Google\Chrome\Application\[current version]\Themes\Windows XP
C:\Documents and Settings\[user]\Local Settings\Application Data\Google\Chrome\Application\[current version]\Themes\
To install the theme simply copy the default.dll you have just downloaded to the above directory. I strongly suggest that you backup your current default.dll file before doing this. Unfortunately, for the time being, there is no way to manage multiple themes. However, this is definitely a promising start form theme developers. I look forward to seeing what’s to come.
Edit 2: Real full screen mode is available in the latest release of Google Chrome. You simply need to press F11.
Edit: For clarification – there is no full-screen mode in Google Chrome yet. This simply opens the browser maximized.
One thing that many users may find frustrating is that Google Chrome opens in window mode. Thankfully there is a simple fix for this. By editing the Google Chrome shortcut, you simply need to add the -start-maximized parameter to the end of the shortcut line.
Your new shortcut line should look something like this:
C:\Users\[user]\AppData\Local\Google\Chrome\Application\chrome.exe -start-maximized
Problem solved! Chrome will now open in full-screen mode.
Google has just opened up Chrome’s dev channel. The dev channel gives early access to new features and bug fixes. Google promises to release Chrome updates to the dev channel frequently, providing webmasters the ability to test their sites and script with the latest version of the Chrome browser.
Google does warn however that dev channel releases are prone to be less stable than their Beta cousins released on the main Google Chrome website.
To subscribe to the dev channel, you simply need to download and install the Google Chrome Channel Chooser. Full details and installation instructions can be found on the dev channel website.
With the release of Google Chrome, John Resig has performed JavaScript benchmark tests on a wide variety of browsers on both Windows Vista and XP. These browsers include:
Testing, using three benchmarking tools; SunSpider, V8 Benchmark, and Dromaeo, has produced some interesting results. Results show that Google Chrome is ahead in all but one benchmark test – very impressive for a browser that is still in its early beta stages. It shows the performance of the new V8 JavaScript engine and the power of the WebKit rendering engine found in both Chrome and Safari.
You can read the full JavaScript Performance Rundown article to see the other (not-so)surprissing results.