Earlier quoted context omitted.
Google's culture breeds internal arrogance and blindness to outside concerns. Arguing with Google people about issues with their products is approximately as effective as arguing with a brick wall.
No, a brick wall doesn't stare at you blankly. Nor does it argue back arrogantly and defy you that whatever Google wants is best.
Why I’m done with Chrome
351–360 of 876 posts
Re: Why I’m done with Chrome
#352I engaged with the folks pushing this feature internally when my own browser started enforcing omnidirectional login. One of my specific complaints was that it was an end-run around the user-provided sync passphrase, which nominally prevents Google from hoovering up my logged-out history. They didn't grok my privacy issue. Maybe they were deliberately misunderstanding me. Doesn't matter either way. Now I use Firefox.
Google's culture breeds internal arrogance and blindness to outside concerns. Arguing with Google people about issues with their products is approximately as effective as arguing with a brick wall.
Re: Why I’m done with Chrome
#353Earlier quoted context omitted.
Why download it in the first place?
A mistaken include in a build file, most likely. I've removed all sorts of dumb stuff slowing down the build that was included by accident or unnecessarily on my project at work. Never attribute to malice ...
This principle is heuristical and as such can result in down-side when one doesn't actually resolve the uncertainty within the heuristic (read: guess) with detailed evidence.
The obvious downside here is that you can accumulate a bunch of risks which each independently satisfy the heuristic, and so don't seem like risks, but in aggregate can result in a swing towards the opposite of what it says.
Meaning, yeah, sure, stupid thing added to the codebase. But with the accumulation of all the poor decisions Google has made surrounding privacy, is Google really that fucking idiotic, or, what?
Re: Why I’m done with Chrome
#354Earlier quoted context omitted.
I love Firefox in theory, it's just that in practice I've never been able to stick with it. One thing or another always leaves me running back to Chrome. It's possible that it's just my own bias and familiarity, but I'm not principled enough to endure an inferior experience in any way. Plus working in chrome dev tools all day long, you really miss it when you want to pop something open and look under the hood real qu…
> Plus working in chrome dev tools all day long, you really miss it when you want to pop something open and look under the hood real quick, and I don't think Firefox is quite up to par there Based on what? What did you try to do and couldn't? Or is your complaint - like the rest of your comment says - that you weren't immediately familiar with the UI, you didn't bother learning, and then decided it was the browser's…
These are not things that Firefox just does differently, they're features that Firefox just doesn't have.
Firefox's dev tools aren't bad in and of themselves. The UX is fine, and getting better. I don't know if other people have opinions about memory tools or profiling -- I don't all that much.
I guess Firefox's dev tools look prettier, and they do have some features that Chrome doesn't. But Firefox features tend to trend more towards, "here's a cool thing like the ability to debug shaders". Chrome's trend more towards, "here's a useful thing like the ability to debug Javascript."
Re: Why I’m done with Chrome
#355Earlier quoted context omitted.
I know this is exactly what you're trying to avoid, but could you upload an example unsigned extension? I'll try to figure it out, could be a bug somewhere.
Thank you for offering to help! I actually just figured out how to fix it right now myself. The solution is to delete the following lines in prefs.js, then restart unbranded-Firefox twice : user_pref("extensions.databaseSchema", 27); user_pref("extensions.e10s.rollout.policy", "50allmpc"); The first start takes longer, so I can tell it's resetting something internally (not sure what). However, the second restart is w…
It's a temporary hack, but you might also want to look at temporarily loading extensions with about:debugging, this works even in official release.
Re: Why I’m done with Chrome
#356Earlier quoted context omitted.
You can run either Firefox ESR or the unbranded builds [1] if you want unsigned extensions, but I'm curious what your concerns are with the unlisted extensions option from Mozilla? 1 - https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded...
> You can run either Firefox ESR Then I have the exact same problem when support dies in the coming months though. > or the unbranded builds [1] Interesting, so does this mean that if I want stable builds, I'd have to manually update to the exact unbranded counterpart of that stable version? > I'm curious what your concerns are with the unlisted extensions option from Mozilla? I guess because I really don't see what…
Good news! Even Firefox ESR 60 always you to disable the mandatory signature checks by setting the "xpinstall.signatures.required" pref = false. The Mozilla add-on wiki was a little unclear, so I just manually verified that the "xpinstall.signatures.required" pref works correctly in Firefox ESR 60. :)
Re: Why I’m done with Chrome
#357Earlier quoted context omitted.
Container tabs just makes up for lack of easy profile switching (at least on macOS, not sure about Windows or Linux), which was in Chrome for years. Even after it came, I gave it a try and found it pretty cumbersome. (Before I get you-can-do-this-and-that replies, I know Profile Manager exists, and that's an ugly hack: macOS users should not need to run multiple copies of the same app bundle.)
Profile switching takes more steps to use than container tabs: 0.
Re: Why I’m done with Chrome
#358Earlier quoted context omitted.
You might want to look into the Brave browser ( https://brave.com ), which is a commercial browser based on the Chromium code, funded by a micropayments idea, which tries to generally be more privacy-sensitive than the Google version. As for a fully open-source version: here's a fairly recent summary (2017) of what's in Chrome and not in Chromium (the open-sourced subset): https://www.howtogeek.com/202825/what%E2%80%…
Does one really want to associate themselves with Brendan Eich though? Brave is what he has been building after being ejected from Mozilla. While Brendan has built some interesting and useful things including Javascript, he is apparently poisonous enough to cause three of Mozilla's board members to resign, including a founding executive of Yahoo, the former CEO of AVG, and the former CEO of Mozilla Corp (from 2008 to…
The other toxic drama was about a 1000$ political donation. Very sad to see an unpopular view used to paint someone as a monster. If democratic political views are enough to kill someones career, it is more a sign of the toxicity of today's social media and activism than a character judgment.
> Does one really want to associate themselves with Brendan Eich though?
No, not really. Not a good political idea to align yourself with the black sheep. With all the tars and feathers he just looks weird.
Though it also works in his favor: Brave is popular amongst the alt-right and technical-minded early adopters. They see it more as character assassination and SJW corporate culture taking desperate vengeance for Trump's win.
Re: Why I’m done with Chrome
#359Earlier quoted context omitted.
Thank you for offering to help! I actually just figured out how to fix it right now myself. The solution is to delete the following lines in prefs.js, then restart unbranded-Firefox twice : user_pref("extensions.databaseSchema", 27); user_pref("extensions.e10s.rollout.policy", "50allmpc"); The first start takes longer, so I can tell it's resetting something internally (not sure what). However, the second restart is w…
Glad to hear you worked it out, good luck! Looking around there are a few levels of cache around whether addons are enabled, I guess those are what you need to clear it. It's a temporary hack, but you might also want to look at temporarily loading extensions with about:debugging, this works even in official release.
Re: Why I’m done with Chrome
#360Did not like how Google forces your google account to be active at all times, and the new UI of Chrome is a regressive step in terms of design.