Joe consumer, comprising an ever increasing majority of the Internet population, simply doesn't care about which browser she is using. More often it is a result of what randomly got installed as the default through their last foray of random clicking and purchases. As a result, Chrome's regular placement on the Google homepage (and IE's default-installation) give it obvious "competitive" edges.
Of course when discussing browser market share this is rarely mentioned, instead popularity is usually attributed to fractional nanosecond differences in rendering time and so on that 99% of users never notice, and simply won't care about even if you told them.
(Edit: there is another reason to appreciate Mozilla in here, in that their efforts seem less focused on branding and positioning than they are much more so on function and vision. Mozilla's endgame shares a certain utilitarian theme compatible with what the masses seem to expect from technology (it's a "computer" with the "Internet" on it, not a "Chromebook" with "Google" on it), than does just about every other company in this space who are using their platforms to sell people more shit they don't need)
However chrome became stable. And then it built on it -- multi processing made one site not crash the browser. Startup speeds were fast, etc. Eventually I switched. It was a minimalistic interface that I could teach to my grandparents. And performance was ALWAYS great.
So the question remains: Switch back to FF? I vote no, until they finally implement what IE has done since IE9 -- multi processing, or solve the damn problem in other ways. Also chrome's sandbox is pretty much unbypassed except for a couple of times in pwn2own (all the exploits are already patched)
Mozilla focusing on the user while google on profit is a point, but it is not a selling point. Show me features. So far chrome's porn mode has been an innovator in the space, and firefox had to hack that mode on to their browser. So from an objective perspective... idk.
But you can't convince people to drop Java if they as much have one site/app depending on it. I'd love to install an alternative non-Oracle Java (not because they're significantly more secure, but to diversify the ecosystem a bit, and to stick it to Oracle for bundling that Ask toolbar), but I haven't figured out how to install them in Win7 yet. (that's not for other people btw, but for the computers at the kids centre I teach)
Still, what I wanted to say, the reason I do give them Chrome (or Firefox, or Opera), is because I'm absolutely unfamiliar with IE, no idea how to enable the proper security settings (or if there are any) and I do want to help many people with an AdBlocker (which also can do wonders for one's Internet security, btw).
There are other good reasons why the security is better, with the only downside being the invasion of privacy, where Google are no worse than others, so pick your poison.
Chrome - McAfee
IE9 - Chrome & Google Toolbar
Firefox - McAfee
Just to add, users rarely choose their car at all. If we're talking about the unwashed masses here, then the primary reason Ford, Toyota, GM, or Volkswagon are popular at all is almost entirely due to happenstance. Joe consumer, comprising an ever increasing majority of the car buying population, simply doesn't care about which car she is driving. More often it is a result of what randomly went up for sale at the corner car lot. As a result, Ford's regular placement on the edge of the car lot give it "competitive" edges.
This highlights your confusion. The set of people that have average computer savvy contains all kinds of races and economic standing. It has nothing to do with "working class," wealth, or racial status and everything to do with computer skills.
> You don't have to have a college degree and a six figure income to be discerning about technology.
I'm not going to point any fingers, but I just want to say someone has some massive insecurities.
> The set of people that have average computer savvy contains all kinds of races and economic standing
How is that different from what I'm saying? Saying the "unwashed masses" don't care about what browser they use is inaccurate. That's all.
To the users, browsers are mostly homogeneous, and choosing one over the other incurs in almost no cost (real or of opportunity). It stands to reason that most people (regardless of class) don't have any incentive to care, and therefore they don't.
The market share of IE (and the usage habits of people of both normal and more advanced tech knowledge) points to the fact that people frequently DO use IE (or safari) because it's pre-installed and only change when it just happens (chrome getting installed and set as default by various other installers being a good example)
The "tech savvy" only differ in one sense: they are incredibly more delusional about their choices than the rest of the planet. I certainly haven't taken the time to study Chrome's design in depth (or for that matter Firefox's), and probably never will. My reasoning for using Firefox is due to a vague-warm-fuzzy ideological alignment I seem to have with Mozilla and their approach to software. Nothing quantitative, and certainly nothing adequately logical that I could use it to command authority over anyone else on the planet. In fact exactly the kind of thought processes that "joe user" experiences ("I like the icon.. it bounces"). 23 years spent in front of a machine, and that's still pretty much me.
but, if someone says that, you know exactly what they mean. seems like a valid response to me any way you slice it.
p.s. this kind of attitude is part of the problem.
To make the example clearer, I've personally had the experience of asking someone what browser they use and getting "Yahoo" (as in the Yahoo.com homepage) as an answer.
How so? It does not tell you if it's Firefox, Chrome, IE, Opera or Safari. My mom refers to the Internet as "google".
that's how she browses the internet then? in her case the application wouldn't matter to greatly if her point of reference is the Google search box
"Joe Sixpack" makes sense to me. Someone who thinks computer experts are elite, and doesn't know much about computers.
The Big 3 made it through the miserable 70's and 80's mostly because they had dealers on every corner while superior Japanese brands were fighting to get lots built anywhere.
But now I'll try Firefox again because of this post. :)
How was it faster than Opera? I have never seen another browser give you the previous page instantly when pressing the back button. Chrome needs to start its spinners for a few ms and then reflow the page, Opera just does it. I'm hoping that, with the move to WebKit, I can switch back to it.
EDIT: I just checked, Firefox does this too. It didn't, at the time that Chrome was released, though.
And the speed people refer to is JavaScript execution. There is no doubt that V8 was much faster than competitors a few years back.
[1]: http://news.ycombinator.com/item?id=5281540 Unfortunately, the original article looks to have been removed.
01 Sep 2008: http://googleblog.blogspot.com/2008/09/fresh-take-on-browser...
TraceMonkey was in the works since late Spring 2008. Apple was also doing more advanced JS performance work before Chrome launched.
V8 had the world-class VM team and at least two years lead (Lars Bak went to Google in 2004; I met him in August 2006 when he was definitely working on V8), so it indeed was fastest at the usual benchmarks, but not by the sometimes-asserted 3x factor.
Maciej Stachowiak of Apple and I were both noting back then how V8's advantage seemed more like 1.3x at the time, but I don't have performance charts from Sep 2008 at hand. Perhaps someone reading does.
V8 got faster over time, as did other engines. Again, it's an excellent piece of work and tops by many measures, but not all -- see http://kripken.github.com/mloc_emscripten_talk/#/17 for two large benchmarks of three where SpiderMonkey beats V8 currently.
/be
I remember, vividly, in Firefox: I would middle-click on a Slashdot link to load it in the background while reading the current one. My focused tab would begin to hesitate and sometimes altogether freeze for several seconds. In Chrome, only the spinning tab would be affected by their bloated DOM.
It took about one year and a half of JavaScript engine development for Chrome to surpass Opera in performance.
Since then, Opera has not been the faster browser anymore.
Try opera, there's a reason he's pointing out that it is different.
Before giving up, and switching to FF, I tried the --disable-gpu --disable-software-rasterizer switches to disable the GPU process but that prevented videos from playing at full speed. Some people here mentioned Chrome runs great on their rigs with 16GB of RAM. But for the rest of the world, Google should force their devs to use Chrome on a machine with a mere 2GB.
How is it that sites like anandtech and investing.com run fine on my old iPhone 3GS, yet take up 256+ MB in Chrome, more RAM than the phone has? Somehow the 3 year old phone loads and displays the sites smooth as butter. Apple is doing something right or Google is doing something terribly wrong to webkit.
You can't install buggy plugins or extensions on your iPhone. Try removing some of your Chrome extensions down and you'll be back in the 50MB range.
It's clear from my own experience, posts here, and benchmarks that Chrome has strayed from it's original design goals of being a lightweight browser. My reference to this iPhone was just to point out that I think it's a issue with Chrome itself, and not the underlining webkit browser.
It's clear that it's fashionable in certain circles to claim this. It's also clear that these claims are based on subjective impressions rather than anything measured, which makes me suspicious given that an effect of that magnitude should be obvious and I haven't seen any sign of it.
If you have actual data showing that the current Chrome browser performs worse than it used to, I'm sure the Chrome development team would love to see it.
The generic argument is empty. Firefox is good for Mozilla's business. Same for Opera.
The business cases for IE and Chrome are significantly different. Distributing IE with Windows benefits users for the same reasons that Ubuntu Linix distros ship with Firefox - they providing a rational and reasonable path from the act of stuffing an install disk into a drive to the point where the user is surfing the internet and possibly completing the installation. IE allows windows to be used right out of the box.
It's hard to make that sort of case for Chrome - but easy for Safari. Chrome was primaily developed to improve Google's data mining and reduce search server loads by collecting keystokes from the address bar.
This statement is not just technically ignorant; it's downright absurd. More than probably any company, Google lives and dies by the web as a platform. Chrome is Google's best way to influence and improve that platform. It's why Google previously had a team of mostly former Mozilla/Netscape employees contributing fulltime to Firefox (including one of the original creators of Firefox), and why that team eventually chose to create Chrome. When the web is so essential to your business, it only makes sense to invest heavily in its improvement, and ensure you have a say in its trajectory.
I'm not saying Chrome is a data-mining tool (though I don't doubt that it could be doing some of that), but it's also not a purely altruistic contribution to the community. Google is the big developer that's doing lots of beautification and really contributing to the growth of the city, but Firefox is the community activist that's trying to make sure all the developers play by the rules that benefit everyone, not just them.
You mean by pushing Google Mail, search, docs and other Google properties.
Netscape was a startup and its founder had a Fuck You Money exit before it met its fate as a corporate subsidiary managed across a continent. The legacy of IE6 lives with us because of suboptimal architectural decisions by web developers. Yet, the web is escaping it - unlike the warts of JavaScript.
There were no IE days before Netscape. Netscape came first, and IE was originally just a defensive response. That's not to deny that there was a period where IE was arguably a superior browser, but IE simply would not have have been created were it not for Netscape becoming the first mainstream browser.
Had Microsoft not shipped a browser with Windows, browsers would have remained obscure shareware like Netscape Navigator and AOL or Compuserve would have been the standard online experience of most people for much longer.
"A new competitor "born" on the Internet is Netscape. Their browser is dominant, with 70% usage share, allowing them to determine which network extensions will catch on. They are pursuing a multi-platform strategy where they move the key API into the client to commoditize the underlying operating system. They have attracted a number of public network operators to use their platform to offer information and directory services. We have to match and beat their offerings including working with MCI, newspapers, and other who are considering their products."
http://www.lettersofnote.com/2011/07/internet-tidal-wave.htm...
He seems to view it as a most serious threat. I think if he thought it would remain non-threatening they would never have made a browser.
70% of browser usage was probably less than 1,000,000 browsers in 1994 and those primarily in large commercial and educational settings. The consumer internet didn't exist because the web wasn't viable at 9600 baud (2738 websites of which 370 were .com in June '94).
http://www.mit.edu/~mkgray/net/web-growth-summary.html
It's obvious that once Microsoft got serious about the web, they quickly moved beyond MCI and newspapers of the memo to a vision of browsers "on every desk and in every home."
http://www.youtube.com/watch?v=tSjfmme4hpM
The scale at which Microsoft distributed browsers made the web commercially viable in the way we know it today. It's easy to forget that Netscape was bundled with AOL - keyword: walled garden.
I bet the adoption was faster that it would have been if microsoft hadn't integrated IE. Of course, if microsoft hadn't integrated IE it's quite possible company would have died by now (or been a footnote of desktop computing history - like IBM). They didn't really have much of a choice.
IE bootstrapped access to Navigator for the general population of computer users. People got Navigator using IE to download it from Netscape's website - just like they get Chrome, Firefox, and Opera today.
Until IE shipped with Windows, the only way a typical user was going to get Netscape was on a floppy disk via the shareware community or perhaps from a BBS. It wasn't being downloaded through AOL or Compuserve and if it was, what would one have done with it August 1995?
It would be naive to ignore Netscape's IPO occurred one week before IE 1.0.
http://en.wikipedia.org/wiki/Internet_Explorer
"0.4 Netscape September 9, 1994 First public beta release" "1.0 Netscape December 15, 1994 First non-beta release"
Is that really more believable than internal corporate interests deciding that it threatened Word?
-- Bill Gates, 1998 a memo to the Office product group[2]
Seems like the guy in charge knew when to actively "stop putting effort into" things and intentionally sabotage the open web when necessary.
I suspect that the corporate interests have long known that IE is not a sales critical feature.
You can blame software designers at Microsoft for that decision (or lack of decision), but I'm fairly sure that dev's at Microsoft are on the "fulfill the design" side of developing...
bubble.....
Please stop this immature behavior.
Though in this case I think maybe there is a third option.. ignorance maybe?
Right? We would have had AJAX and DHTML so much sooner if it wasn't for Microsoft holding things back.
I personally didn't buy the whole Chrome hype when it came out, and stayed with Firefox, observing how Mozilla gradually made it much better.
There's a flip side to this coin; Firefox exists to support Mozilla's main business, which is the web.
This also means that Mozilla staunchly and without fail opposes any technological shift that could unseat the entrenched market position of the existing web technology stack, even if it would improve things for end users.
Google developed SPDY, NaCL, Dart, all in an effort to improve the underlying constraints of delivering code/information -- in any form -- to users.
If we only had Mozilla, we'd be locked into HTTP/HTML/CSS/DOM/JS forever. Technology has to evolve to move forward, but Mozilla has very little reason to want the web to evolve.
Mozilla, Apple, and Microsoft will not implement NaCl and Dart because they feel that they are technically worse than alternatives (asm.js and either ES6 or compiling other languages to JS).
The technical problems will ultimately provide a worse experience to end users. For example, NaCl is not portable, meaning that users' apps will not work on all the users' devices like they expect, and PNaCl is not backwards compatible, so the apps won't work on all browsers. Dart threatens to make garbage collection slower because of cross-language cycle collection, which results in a worse experience to end users.
Mozilla has every reason to want the Web to evolve. If the Web doesn't evolve and loses to native platforms, Mozilla becomes irrelevant and dies. How is that not incentive?
After Google designed it, developed it, and then deployed it to their properties. And even then Mozilla was still questioning whether it should be implemented, because "would anyone use it?".
> Mozilla, Apple, and Microsoft will not implement NaCl and Dart because they feel that they are technically worse than alternatives (asm.js and either ES6 or compiling other languages to JS).
We fundamentally disagree on that. I see NaCL as a route to the future of haardware-supported sandboxing, in the same way that virtualization was. NaCL is a way to fundamentally re-invision how we implement sandboxing of process, and move beyond the legacy ring-0 design.
asm.js is just another application-level hack on top of a huge pile of application-level hacks. It's time to coalesce the stack of these hacky abstractions, and clean up shop.
> For example, NaCl is not portable, meaning that users' apps will not work on all the users' devices like they expect, and PNaCl is not backwards compatible, so the apps won't work on all browsers.
So what? You know what happens when I fire up a PPC Mac from 1998 and try to use Netscape 4 on the modern web? Nothing works.
At least something like PNaCL has a MUCH smaller surface area than something like the full HTML/DOM/CSS/JS stack, which makes supporting it in a backwards compatible manner indefinitely far, far easier.
> Mozilla has every reason to want the Web to evolve. If the Web doesn't evolve and loses to native platforms, Mozilla becomes irrelevant and dies. How is that not incentive?
Because the web needs to evolve away from what it currently is, and that's the one thing Mozilla ideologically doesn't want and won't do.
PNaCl, to interact with the world, uses Pepper. Pepper is a huge surface area, comparable with the web stack in size.
It's neither comparable in size or complexity to the entire browser stack. CSS, HTML, DOM, and JavaScript are so large that they that require the full weight of large-scale corporations to provide a working implementation that's even remotely compatible with the web as its deployed today.
Mozilla received a leg-up in terms of having the majority of the code donated by a large corporation, and by having the web be compatible with that existing technology stack. I can see how I could spend $1M and have a team implement the Pepper API in 6-12 months, and that includes an independent implementation of NaCL/PNaCL sandboxing (if we leveraged google's development tools).
I can't even begin to imagine trying to create an independent browser stack for any reasonable amount of money.
[edit] This is the current Pepper API documentation:
https://developers.google.com/native-client/peppercpp/inheri...
It's tiny.
Pepper, NaCL, et al also collapse a huge number of complex and nuanced layered web abstractions back down to the approachable problem of running somewhat arbitrary user code, at speed, in a relatively open and loosely define environment.
That's the same environment that projects like Mozilla needed to ever have the chance of producing a web browser in the first place. It sure seems to me that you guys -- consciously or not -- have divided the market into 'browser makers' and 'non-browser makers', and then decided to constrain the tooling and power available to everyone that is not a browser maker.
This can't be healthy for the internet.
NaCl is something new. It isn't meant to render documents. It sandboxes native code.
Both the web and NaCl are great, just for different things.
Well, now we're getting to the core of it! :)
I agree! I think the web should stick to rendering documents, which it has always done reasonably well, and leave applications to technologies such as NaCL, which people can use to produce the next web browser.
[1] NaCL and the future of hardware, Google's investment in SPDY, surface area of NaCL's complexity, evolution of the web ...
Each of these does not threaten the importance of the browser. On the contrary, they both widen the use cases of the browser and raise the entry barrier for competing browsers. These effects protect Mozilla, instead of threatening Mozilla.
On the other hand, Google pushes OAuth single sign-on against Google accounts, whereas Mozilla is pushing Mozilla Persona, a distributed, no-central-authority SSO for the web.
I conclude the exact opposite of what you state. If we use Chrome, we're locked into technologies that serve Google, if we use Firefox we're pushing open technologies.
What? Mozilla very much has a reason to want the web to evolve, in order to stay competitive with the various non-web mobile app ecosystems.
If you accept 'the web' as more of a conceptual ideal of openness, then there's a lot more room for innovation.
The problem is, at its core, that the people who are best suited to change the way the web works, are the developers that stuck it out through learning JavaScript, HTML, CSS, and browser quirks, and then spent the years required on top of that to begin working on the browsers themselves.
Of that self-selecting group, how many of them are likely to want to voluntarily rework and/or abandon core web technologies?
On the other hand, Chrome, existing to further Google's interests, has every reason to employ whatever creative technology solutions are necessary to improve the user experience, even if that means changing or abandoning the legacy web technology stack in the process.
The most popular alternatives to Firefox are Google's Chrome and Microsoft's Internet Explorer. I doubt these alternative browsers would exist if they were not useful for Google's and Microsofts main businesses. These companies produce web browsers to support their main products/services. The rationale behind AOL Explorer (https://en.wikipedia.org/wiki/AOL_Browser) was similar. In settings like those privacy and other interests of web users are easily sacrificed.
Out of all the big browsers, Mozilla Firefox comes closest to being a web browser for the sake of web browsing.