Chrome is where it's at anyway.
post #21 of 47
12/18/09 at 1:07pm
Mosaic was the first graphical web browser. It was born in the early ’90s, created by a small team headed by Marc Andreessen. The same crew would go on to found Netscape Communications and build the Netscape browser, which would eventually lead to the Mozilla browser, and finally to Firefox. So, running Mosaic is basically taking the browsing experience all the way back to its roots.
Dipert acknowledges the work of two other coders who ported the old code to run on the modern Linux: Sean MacLennan and Alan Wylie. As MacLennan says on his site, “If you are going to run a 10-year old protocol (HTML), you might as well use a 10-year old browser.”
Spinner Count: Upon starting Firefox, the spinner graphic is shown (and disappears) a total of three times, meanwhile in Chrome the graphic is only shown twice.
Window Drawing: In Firefox, the window is drawn (animated to size), then the browser chrome is drawn, then the website is drawn. In Chrome, the window and browser chrome is drawn all at once and then the web- site is drawn. This helps Chrome to feel faster because there is less visually going on at different times. Firefox feels very sequential in it’s loading, while Chrome seems to do everything at once. This allows Chrome to feel fast because once the window is animated the size, everything is pretty much ready to go. This is especially true if google.com is set as your homepage on Chrome.
Webpage Drawing: In Chrome the webpage loading icon is fairly small and is never ‘fully’ seen. While in Firefox the loading icon is large, grey, and can always be seen in it’s entirety. This is visually ‘bloated’ and makes Firefox seems slower. Furthermore, because Chrome’s loading icon animation goes ‘around’ faster, Firefox’s loading icon takes more time (seemingly) to get ‘around’.
Page Title: In Firefox, a page’s title is shown on the tab right away, while in Chrome the title is not shown un- til the website has completed loading. This is a simple trick that allows Chrome to feel faster in that once the title is shown, the page is ready. While in Firefox, a page’s title makes it seem like a page has loaded but in fact the page isn’t ready to be interacted with quite yet and the user has to ‘wait longer’.