I'm still kind of bitter with the way they did that. A lot of windows installers, which usually installed you toolbars if you forgot to uncheck a box, started installing chrome as your default browser if you forgot to uncheck a box.
I've seen a lot of non-technical people using chrome who have no idea what chrome is or remembering giving consent to installing chrome.
Google was paying out $1 per Chrome install for a long time, which is why you saw it being heavily distributed through all sorts of shady channels like monetized installers.
For context, a payout of $0.10 for a bundled install would have been considered really good back then; a payout 10x that amount meant you'd pull every dirty trick in the book to get as many installs as possible.
anywhere i go without an adblocker begs me to install chrome and stop using whatever horrible outdated browser im using (according to the google ad), and how youtube, etc work best with chrome anyway
thats quite a lot of powerful advertisement, on the sites people browse every day. its not too different than being part of the default install IMO ;-)
and of course - chrome is a pretty good browser (though edge is actually quite good and firefox is pretty much ok as well despite not yet doing sandboxing)
And the thing is it's sadly not a lie. YouTube and such do work best with Chrome. Google's effective web vertical integration means they control every stage of the pipeline. They control the sites and the browser. They can deploy experimental tech in Chrome which nobody knows about and which only Google sites use.
One example of "google only APIs" that I ran into recently is the chrome extension browserAction.openPopup API. This API is whitelisted (in stable) for use by the Google Cast extension. Extensions authored outside of Google cannot use it. This is creates an uneven playing field.
That's nothing. One of the biggest injustices with Google Cast is that capturing system audio on Android is a whitelisted system-only permission and only Google Cast (and a couple system apps) are allowed access to this. Somehow screen video capture isn't a system-only permission.
Nobody other than Google (or your OEM) is allowed to build complete screen casting apps on Android. All third party solutions require you to output your audio through your speaker and capture it with your microphone, which is much worse quality, single-channel, and makes sound (I want to hear my device audio through the speakers of the device I'm casting it to).
It makes no sense, especially when any device on your network can emulate being a Miracast receiver and get access to the same audio data that you aren't allowed to access on your own device. In fact, Windows 10 insider preview currently includes a Miracast emulator just for this purpose of Android screen sharing.
"The popup is anchored to the extension icon, which might be in overflow or not even exist, in which case it is anchored to the Wrench menu. That kind of anchoring would make the message in the popup to appear to be from the Chrome browser (since it points to the chrome UI) and would present a vector for tricking users into thinking the message is from a trusted source.
Since this is not safe to allow all extensions to do we'd need a lot better reasoning than "I'd like to use this in my extension" before allowing widespread use of this API."
I agree that the API limitation is most likely not malicious and I did not intend to imply otherwise. Still, lack of malice does not change the fact that the Google Cast extension has a competitive advantage over other non-Google extensions (which can't use all of the same APIs).
"While the Philips Hue system is based on open technologies we are not able to ensure all products from other brands are tested and fully interoperable with all of our software updates. For guaranteed compatibility you need to use Philips Hue or certified Friends of Hue products."
After all, it'd just be downright unthinkable that any non-Philips lightbulb should be compatible with our light sockets, that any brand of plug should fit into our wall sockets, or that non-Google-branded plug-in should be able to use a web browser's APIs... I mean, goodness, next we'll be thinking that the term "plug-in API" suggests its supposed to allow things that other people created to interoperate...
They've already been hit with that in the EU. And, I imagine the first thing after this current election cycle in the US ends will be newly minted (or newly defrocked, as the case may be) politicians attempting to take a cheap shot at Google -- especially since Popular Luddism is circling the political backwaters these days.
At some point, YouTube worked better with Safari than with Chrome or Firefox. YouTube would serve VP9 to browsers that supported it, but it was not hardware accelerated, so it used much more CPU.
Exactly. They used shady advertising technics to get Chrome installs, but now that they have them they paint themselves as the anti-spam warriors. Yet, every time I point out on hacker news how big hypocrites they are for saying their moto is "don't do evil", I get downvoted. It's frustrating to see a shady company having such a bullet proof brand. I hope this will change some day.
It also had an advantage of being a friggin' fast browser. I switched in 2009 and never looked back beside occasionally trying out FF and nope'ing back to Chrome.
When talking about a piece of software as complicated as a modern browser, “became faster” is too broad to have any meaning at all — you can find specific features where almost any browser is faster.
In the case of Chrome and Firefox, they're competitive enough that you really need to say both what you're measuring and how you measured it. People tend to say one is faster than the other when they most commonly mean “the set of extensions I installed in A slowed it down more than B”.
No, we are talking about the architecture of the browsers in areas where there is significant impact (ie. UI Responsiveness), this has nothing to do with extensions.
In Chrome when you load a JS-intensive website (ex. Facebook) you can switch to a different tab while the website finishes doing that JS-intensive task (ex. loading), but in Firefox the opposite happens, the entire browser freezes so you are forced to wait until the browser becomes responsive again.
We are talking in the order of magnitude of milliseconds, but unfortunately it is enough to be perceptible (and annoying).
Fortunately for FF, e10s[1] is almost baked, it still doesn't feel as responsive as Chrome BUT it feels significantly better so you can easily neglect the difference until it matures or something better (Servo[2]) gets baked.
That may be what you thought we're talking about but the comment I replied to was simply “Firefox became faster than Chrome quite a while ago already”.
My point was simply that without providing more detail, those comments are so vague to be useless.
This. I love FF and use it wherever I can, but there are small tricks in Chrome that make it seem much faster in normal use. No matter what you do, action feedback is instant. Firefox should really imitate this.
I have a policy of keeping personal browsing on chrome and work based browsing on FF. Every now and then FF will inexplicably hang for over 5 seconds on a page that is probably already cached. I never notice this on chrome, and my connection speed is over 100MBps..
Other times, FF is lightning quick - near instantaneous loads - only other thing I can think of is that I'm running FF on Fedora?
Honestly I just like Chrome's UI better... I have to use IE/Edge, Chrome, Safari and Firefox regularly to test things... I keep coming back.
I had higher hopes for FF android, as it allows plugins (adblock), but the browser is so horrible on the platform, I wound up switching back... I also tried dolphin for a while. Neither was satisfactory.
My experience in Android is a different one, I'm using a FF fork (Adblock Browser) and my mobile life has never been better.
Unfortunately outside America the mobile web is a malvertising minefield, and the malvertisers target the carriers directly, so there is no way to expect ad networks (ex. AdSense) to proactively hunt for them.
A browser with integrated AdBlock is the most sensible option you can have in a non-rooted device, and the easiest one you can recommend to friends and colleagues.
Do you happen to use lastpass? Is there an integration there either with the android app, or with the browser itself that works? I'm just curious as the chrome app can tell what url is in the browser, and peak into the page... This detail doesn't work in ff, dolphin and others I've tried so far.
I know that is a separate issue... would really like my password manager & adblock & the app window/tabs where each "tab" is a separate window instead of integrated tab-bar, which isn't very nice at all on a phone.
Adobe Flash - When you download and installed Flash for Opera or Firefox, it would trick you into installing Chrome as your default browser unless you noticed and unchecked a box: http://i.imgur.com/Uldw6X3.png
Java - When updating, Java on Windows would often trick you into installing Chrome as your default browser unless you noticed and unchecked a box
Avast, AntiVir, etc - Nearly every free antivirus on Windows was paid by Google to install Chrome. The free antivirus would notify you there was a new version and if you clicked the UPDATE or CONTINUE button without noticing and unchecking the box, you'd wind up with Chrome installed and set as your default browser: http://i.imgur.com/hNZLbmL.jpg
The majority of the non-techies I know and had set up with Firefox have no idea how Chrome got on their machines and became their default browser. I'd wager a lot of Chrome's desktop userbase on Windows is due to shady bundleware arrangements.
Chrome was still engaged in the above behavior the last time I checked.
Which is why I install Unchecky on friends' and relatives' machines. It automatically unchecks all those default boxes and avoids not just Chrome but whole heaps of crapware...
Google is certainly not blameless here. If they had banned partners who's installers violated a reasonable set of terms, e.g. opt in instead of opt out, this would not be an issue. They would have gotten free installs until the bad installer was fixed and verified ;)
So does Intel and many other "trusted" vendors, we all know about the power of default values.
As I said, people shouldn't be upset at Google, installing Chrome was a significant improvement, or would you rather see IE8 still as the dominant browser?
I blame Adobe, Oracle, etc. because they have the trust of the users and a piece of software considered essential by many people, yet they decide to use the shady practices that cheapskates use.
If it weren't Chrome it would be the dreaded Ask Toolbar or something even worse, so it's not the fault of Google, quite the contrary, installing Chrome as a byproduct is possibly the least negative outcome.
Of course you should be blaming Google. They are a willing participant in deceptive bundleware. And it is specifically included in the download for Adobe Flash for Firefox/Opera Classic (aka, not IE's Flash which is different), so it is setup to steal users away from competitors. At least the last time I checked, and as demonstrated in my screenshot above.
You talk as if you knew the terms of their deal and corroborated that Google asked to target every browser, in my experience these kind of deals are offered as "all-or-nothing", so having Firefox or Opera targeted were a side effect.
If you suggest the opposite, you don't do web development or live in the early 2000's.
> Across the board they are entitled to make that decision for every user?
Saying "every" is an exaggeration, since several users would opt-out. Installing a better (yes, better) browser to technically-impaired people who don't even know what a browser is looks like a good trade off to me.
> it is absolutely as bad as any of the crapware vendors who do this. Google is just as bad as the ask toolbar people.
Ask is a dying company doing questionable last ditch efforts. Google is a healthy company deliberately tweaking tech-impaired user's defaults, there is a difference whether you like it or not.
Adobe is guilty of this. If you download Flash Player from their site, the "Optional offers" are to also install Chrome and Google Toolbar. Both of which are checked by default.
Parent isn't saying Google didn't pay (I'm sure they paid per install) -- just that Adobe is guilty of allowing these sleazy auto-install offers which Google took advantage of.
I prefer to use Firefox. I ended up switching because Netflix refused to work in Linux unless I used Chrome. At that point there was no point having two browsers installed so was path of least resistance just to use chrome for everything.
I'm still kind of bitter with the way they did that. A lot of windows installers, which usually installed you toolbars if you forgot to uncheck a box, started installing chrome as your default browser if you forgot to uncheck a box.
I've seen a lot of non-technical people using chrome who have no idea what chrome is or remembering giving consent to installing chrome.