Chrome Becoming World's Second Most Popular Web Browser
redletterdave writes with news that Google Chrome is in the process of surpassing Firefox to become the second most popular web browser. Pinpointing the exact time of the change is difficult, of course, since different analytics firms collect slightly different data. The current crop of media reports were triggered by data from StatCounter, which shows Chrome at 25.69% and Firefox at 25.23% for November. Data from Net Applications shows Firefox still holding a 4% lead, but the trends suggest it will evaporate within a few months.
And still Mozilla doesn't get a clue that some of the recent changes are driving away users. Amazing.
Discussion System prefs link: http://slashdot.org/users.pl?op=editcomm
I'm not saying that Chrome is not a good browser, but, what happened IMHO is not that Chrome is getting better, instead, FF is getting worse every day.
I do not know how the Flash Plugin in a browser can suddenly take the 90% of a i7 CPU.
FF people forgot what made them succeed: simplicity.
When Firefox appeared on the scene, it gave Microsoft the kick up the arse it needed to improve their crappy, aging browser.
When Chrome appeared on the scene, it gave Mozilla the kick up the arse it needed to improve their crappy, aging browser.
It'll be interesting to see if the same thing happens in a few years with IE.
Summation 2
Do you know what changed between FF4 and FF10? Almost nothing! Really! From FF6 to FF10 it is nothing for sure. But they managed to break addon compability 7 times in between. So, from what I understood, we were going to have releases from often so that we could get more features more frequently. We got nothing! Or almost nothing. I jumped of from FF6 to Chrome and I lived happily ever after. By the way, 5% of the Internet users are stuck with the outdated FF3.6 today, without the HTML5 advances of FF4 and FF6, because of this new release process. It is as if we need another browser vendor holding the web back. Thank you Mozilla.
Chrome is popular partly because of three things: it's new, users are ignorant (below), and the Chrome plugin API[0] allows the browser to do some really fast, but braindead[1], crap (aka ActiveX/IE) like running native system code in a sandbox.
Re Ignorance: There has been a lot of misunderstanding towards mozilla "memory usage" over the years because users can't figure out that each of the 100 tabs they have open consumes a certain amount of memory. And several of those tabs, running Adobe Flash in the background, simply bring their system to it's knees.
Yeah, chrome is snazzy, and Mozilla does some brain dead stuff too, but I trust them more than Google. Furthermore, segregation in the market space is actually a really, really, really good thing for the consumer.
[0] - http://www.theregister.co.uk/2010/06/25/mozilla_on_npapi_pepper/
[1] - http://www.tech.slashdot.org/story/11/10/24/151238/bug-opens-chrome-to-easy-remote-code-execution
Join the Slashcott! Feb 10 thru Feb 17!
Google's views on privacy. Maybe my view is born of ignorance about what Chrome actually does track vs. doesn't track, but as of now I just can't trust them enough to use that browser all the time. I can't get past the, "Just don't do anything wrong..." comments by the Google leadership a while back.
I trust Firefox with my privacy rights more than I trust Google, which is simply an advertising company.
I like Chrome, but until Adblock works as well as it does on Firefox I'm not interested. I'm not willing to watch Youtube commercials.
Exactly. Their main objective at the outset was to "take back the web". The shape of this graph, where it comes back from monopoly around 2004, is because of Firefox. We all have good reason to be thankful.
Microsoft's stranglehold on the market let them define the standards including not make any progress for 5 damned years. Stuck with cross-browser incompatibilities, stuck without technological progress or many of the features we take for granted these days, stuck with a browser that got everyone's system hacked and ate up countless geek hours with reinstalls. Man, what a nightmare.
And it wasn't just Microsoft's fault. It was also the fault of the users who did not opt for a heterogeneous browser ecosystem. Granted, it's a lot to ask the average person to defend a "heterogeneous browser ecosystem", but at least the geeks (and epidemiologists) should get it. And if you don't, let me spell it out for you: Don't push us towards browser monoculture . Not again, please. That sucked.
Once Chrome gets the breadth of plugins that Firefox has, it'll be no better than Firefox.
Modern Firefox is virtually as fast as Chrome and actually uses less memory than Chrome. `The problem is that many Firefox extensions leak memory and really slow Firefox down. The reason that Chrome's plugins don't is that Chrome plugins simply aren't allowed to do a lot of the things that Firefox extensions do.
I switched to Opera just 2 days ago and it blew my mind. It's fast, lightweight and does everything you need and nothing more. It's what firefox used to be before it jumped the shark.
AdBlock Plus runs on Chrome. It's in Google's Chrome Web Store.
Get back to me when they have a fully functioning NoScript.
The Slashdot bandwagon immediately sees the opportunity to point out that "Firefox sucks because 8.0 should be called 5.0.3" and you reveal the real reason that Chrome is everywhere: They're bundling it with bloody well everything but the kitchen sink and the same lemmings that used IE6 until recently are now finding Chrome icons on their desktops.
And fully functioning adblock plus. Because right now, it sucks.
There's a "good" side to mac-like behavior?
Two of my imaginary friends reproduced once
How difficult is it to set a stable extensions API, make extension developers aware of it, and then making the browser get out of the way?
It's very difficult, with certain types of extension APIs.
We could just drop the current extension API entirely and replace it with one like Chrome has. That would make things much simpler, it could be stable, there would be no way for extensions to leak memory or slow down the browser, and the browser could auto-update very easily. However, that means throwing out all the current extensions that Firefox has. Worse, that new extension API would not allow recreating all the current extensions either - stable, safe extension APIs are necessarily more limiting: They are stable and safe because they don't let extensions do everything. The upside is safety and stability, the downside is the addons are less powerful, that is they can do less. As one example, Firefox addons can radically change how the browser looks, Chrome addons cannot. There is a tradeoff here, I am not saying one approach is better than the other, but just that you can't have everything.
Firefox is taking two paths here: First, we are adding a new, safe&stable extension API (Jetpack addons). But we are also keeping the existing one, and making a lot of complex changes to the browser to allow those addons to be updated automatically etc., so the current downsides are less troublesome. That takes time, but each release is an improvement (in the number of addons that can auto-update, for example).