New Posts  All Forums:Forum Nav:

faster browser? - Page 2

post #21 of 47
Chrome is where it's at anyway.
post #22 of 47
Quote:
Originally Posted by Steve View Post
Chrome is where it's at anyway.
Yep -

"...for all of Chrome's gains, it remains far behind both Microsoft's Internet Explorer (IE) -- which runs only on Windows -- and Firefox, the world's No. 1 and No. 2 browsers. During November, IE had a 63.6% share, while Firefox's was 24.7%."

and ...

competing for 3rd place against Safari

cheers ...
post #23 of 47
I still wonder a bit if safari is #3/4 because Safari is the IE of Macs. As much as I like Chrome's speed, it's not fast enough compared to FF to justify the lack of extensions+themes. People also like to claim that Chrome gives you the most realestate for browsing...well FF gives you the same amount if you hotkey enable/disable the menu bar. And Chrome does startup faster, again because it has no extensions or plugins (flash, shockwave, .net, silverlight, divx, etc) to run. FF starts just as fast with a new "clean" profile.
post #24 of 47
Google Chrome v5.x now allows the use of add-on and extensions. We shall see if it still be the "fastest" as it claims

My 1st test run of last week tells me that Google needs to work on this. But no fear, they will take the work from Mozilla and tweak it fast

cheers ...
post #25 of 47

Google share gained. IE and FF slipped.

Chrome Gains in January 2010 - Takes Share from Internet Explorer and Firefox

The Google Chrome browser gained .6% of global usage share in January. Both Firefox and Internet Explorer dropped share during the last month.

Statistics.

cheers ...
post #26 of 47

Google gaining in Feb 2010

... not counting that it sees the download number increases since the implementation of Windows Browser Dialog.

Chrome Only Major Browser to Gain Usage Share in February

The Google Chrome browser gained .4% of global usage share in January. All other major browsers showed a month-to-month decline.



Source.

cheers ...
post #27 of 47

Browse the Web as it Looked in 1993

Quote:
...
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.”


Nostalgie at its best

cheers ...
post #28 of 47
I am not a huge fan of Chrome. It's lightweight for sure but not really feature rich.
I prefer Firefox 3.5 as it is very fast and I can still have the addons that I need.
post #29 of 47
Don't you want to move up to FF 3.6?

cheers ...
post #30 of 47
Crediting warden26 for coming across this statistic link

Period Mar09-Apr10:
- IE & Opera downward
- FF, Chrome and Safari upward

cheers ...
post #31 of 47
I really enjoy the last 2 days of Firefox Minefield builds. Solid, quick and easy to the eyes with the rendering. If only the add-ons can keep up with the version changes.

cheers ...
post #32 of 47

Perceived Speed Performance

Perceived Speed Performance

An interesting blog read about Firefox vs Google Chrome load.

An extract:

Quote:
General Observations

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’.
cheers ...
post #33 of 47

HTML5 Speed Test

... Firefox > IE9 > Opera > Google Chrome ...

http://www.youtube.com/watch?v=OIZUdZdFzOo

...
post #34 of 47
I must add this as it enables GPU employment for chrome 7 builds (and chrome canary, and chromium)

How to Turn on your GPU in chrome 7 dev, canary, and chromium builds
  1. make a shortcut for chrome / chrome canary / chromium on desktop
  2. right click it and go to properties
  3. find where the target is and paste "C:\Users\insertusernamehere\AppData\Local\Google\Chrom\Application\chrome.exe " ---enable-gpu-plugin --enable-gpu-rendering --enable-accelerated-2d-canvas --enable-accelerated-compositing --enable-video-layering --enable-webgl --enable-fastback
  4. after adding the cmd information post-quotes, close and restart chrome
  5. reopen fishIE test... you should see quite a healthy jump in FPS (NB: this cmd i listed is the one for the chrome dev, below is the one for chrome canary)

    NB: if you are using canary, it will look like this:
    "C:\Users\insertusernamehere\AppData\Local\Google\Chrome SxS\Application\chrome.exe" ---enable-gpu-plugin --enable-gpu-rendering --enable-accelerated-2d-canvas --enable-accelerated-compositing --enable-video-layering --enable-webgl --enable-fastback in your "target" field when you go to the shortcut's properties. However, it should also give a noticeable GPU boost as well.

    Chromium is this in the "target" on the desktop shortcut's properties (ie: put this long sequence in the "target" on the shortcut's property page.

    "C:\Users\insertusernamehere\AppData\Local\Chromium\Application\chrome.exe" ---enable-gpu-plugin --enable-gpu-rendering --enable-accelerated-2d-canvas --enable-accelerated-compositing --enable-video-layering --enable-webgl --enable-fastback

    Hope this helps

    Jason




post #35 of 47
What are the benefits of doing this?
post #36 of 47
Quote:
Originally Posted by Steve View Post
What are the benefits of doing this?
OK, here's the logic.

As webpages and online games become increasingly 3D intensive, it is only now that the GPU has become involved in any way with the online experience. IE9 Beta and Firefox 4.0b7pre have this natively turned on without needing any user input, but Chrome doesn't. So you use the above sequence i typed out for this reason:

If we look at these 3D apps in chrome, chrome by default doesn't have its GPU acceleration turned on. GPU acceleration means that the GPU is involved in both processing and in the graphics rendering of that particular page. Additionally, a GPU is like a very tiny supercomputer with hundreds of cores, its own onboard RAM, a great deal of available bandwidth, etc. However, chrome doesn't "know" this, so you have to tell it. In its default state (GPU Acceleration "off"), it's no more performance-capable than if one were to remove the GPU outright and run on an IGP.

Pics of this to come.

Now, from the attachments (must be logged in to see), we can see that the GPU is essential in not only benchmarks, but can be extrapolated to graphics intensive activities. (The 1000 fish test is key). Without the GPU, we get 3 fps, with it... 33fps. The Psychedelic whirly test is the same. WIthout it, we get 13 revolutions / minute... with it, 1,769. Thus, the GPU is important as a means of not only frames per second, but how fast pixels can dynamically be made to change color. (Think of it as twisting the rainbow card... if you can get it to turn fast enough, congratulations it turned white.... same test, just more modern). The speed read test is also GPU accelerated. We can see that in the 60fps buffer being hit, with 13ms as the avg refresh rate, suggesting that without a limiter, the rate would be closer to 75 to 80 fps. Without the GPU, we get approximately 80ms per change, and 12 fps. Thus proving, at least in some small way that the GPU is key not only in video games, but with the advent of CSS3, HTML5, and increasingly complex graphics, the world wide web could become very GPU oriented in the years to come.

Specs:
Browser: Chrome 7.0.524.0 Canary Build (AKA Chrome sxs)
Laptop: Sager NP8662 in signature
Driver: nVidia Geforce 258.96 Verde Drivers
Aero and GUI Goodies: ON
LL
LL
LL
LL
LL
LL
post #37 of 47
So this would work great with Google Earth maybe? Can you run Earth in chrome?
post #38 of 47
you can, but i think you have to DL earth to get it
post #39 of 47

October 2010 Market Shares

...


- IE, FF, Opera slipped
- Chrome, Safari gained ..

More ..

cheers ...
LL
post #40 of 47
overall, it looks like IE and Firefox are slowly losing ground and that Chrome is gaining.
New Posts  All Forums:Forum Nav: