171–180 of 203 posts
Earlier quoted context omitted.
Or you can install the multi-account containers add-on in FF57: https://addons.mozilla.org/en-US/firefox/addon/multi-account...
Do you know what the difference is between this extension and the native support in FF57? It seems to me they are one and the same. Could it be this was an extension that is now natively part of FF Quantum?
I really like container tabs (you have to enable them in about:config - privacy.userContext.enabled and privacy.userContext.ui.enabled). It allows me to have multiple AWS accounts open at the same time without having 2 different browsers or one account open in private mode. I have 2 main containers I use: production and staging.
Chrome has this as a first-class feature, "People." I have one window open for personal, and another for each of the AWS accounts I have access to. Sounds from your description like FF can do this at the tab level?
Firefox also has profiles (about:profiles) but with less UI around it so it's annoying to use.
Earlier quoted context omitted.
Yea, firefox has profiles as well. Containers are different and apply your browsing context based on the tab. Super useful, you can also configure sites to open in a certain container. I do wish I could just pin an entire window to a container, but overall the flexibility is worth it. (I abhor having more than one window open per app at a time.)
I am unfamiliar with it, but the profile manager in FF does not seem to be on the same level as Chrome. In Chrome you can change the profile and reopen your previous tabs by clicking in the top right. With FF, you have to quit FF and type in the terminal 'firefox -P'. They are not at the same level. https://support.mozilla.org/en-US/kb/profile-manager-create-... Containers are really bad at saving your workspace: tab…
> Containers are really bad at saving your workspace: tabs with a profile so I can just shut down work at the end of the day or on a weekend.
Sure they are, ensure your "open tabs from last time" pref is selected in settings.
Me, far too many times. Everytime there's a "Why you should use Firefox" or" Using FF is the right thing to do" post on hackernews, I gave FF a chance, only to be disappointed and go back to Chrome. However, a few weeks ago, I decided to try out FF Quantum (aka FF 57, vanilla, non dev edition) after hearing it repeatedly in /r/rust and hackernews. I was immediately hooked with how fast it is at rendering pages. Now,…
Also, the devtools are actually a React app (https://github.com/devtools-html/debugger.html), and this means that you can hack on them using ... your devtools (and any other HTML/JS/React tooling you like)! And you can hack on them in any browser, and use them to debug any browser (however some browsers may not support the same debugger protocol features the Firefox devtools support). They're super easy to work on and it's really fun.
(Of course, there's also a devtools "server" on the firefox side that responds to the queries of the React devtools client, and hacking on that is harder, but a lot of the stuff can be done without needing to touch this)
I downloaded FF today, it's zippy. But I rely on dozens of Chrome extensions. That's one of the things I like about Chrome -- its extensibility. HOwever, Chrome is a memory hog, it routinely destroys the 16gb of memory and the battery of my MBPro. When FF has sn equivalent set of extensions, I will happily dump Chrome. Until then, it appears I'm stuck with Chrome
https://addons.mozilla.org/en-US/firefox/addon/chrome-store-... may help converting the format.
Extensions which are incompatible can usually be ported with minor changes; IIRC at this point Firefox has all the APIs chrome does (and more), however certain things slightly differ (e.g. the chrome.foo API is browser.foo in firefox).
I tried (again) to switch to FF yesterday when 57 was released, and unfortunately still ran into a known bug that makes it practically unusable for me: FF treats underscores as punctuation that breaks up a word, so given text "foo_bar", if you double click on "foo" or "bar", it doesn't select the entire word. This goes against all conventions of Chrome, other text editors, etc. It seems trivial, but as developers we…
Earlier quoted context omitted.
I believe that no information about user actions and behaviors should be recorded by a browser. It does not benefit the user in any way, only Google and advertisers. Also we should remember that data needs to be stored first before it is aggregated. What happens with information about each single event?
> It does not benefit the user in any way Really? The browser-maker learning what features people use vs. don't, or what features are fast vs. slow on actual user machines, doesn't benefit the user by getting them a better browser over time? I would like it if the statistics from Chrome in particular, were sent to Chromium-project servers rather than Google servers, though. Even if only Google's derivative of Chromiu…
It's hard because if (due to a bug) something were not correctly aggregated and anonymized, then their private data would leak to the public.
They are also worried about the non-tech press going through the metrics and making misguided headlines like "Google says 66 percent of Chrome users have been targeted by russian malware, and even more in the USA!"
Yep. Like to see some competition and I’m a huge fan of rust, so like to support it any way I can. I hit minor compatibility issues on some sites, but it’s rare. Main thing I miss is auto shrinking tabs. FF doesn’t support the bajillion tabs methodology so well right now.
But maybe you can get it more to your liking by tweaking browser.tabs.tab in about:config?
Me, far too many times. Everytime there's a "Why you should use Firefox" or" Using FF is the right thing to do" post on hackernews, I gave FF a chance, only to be disappointed and go back to Chrome. However, a few weeks ago, I decided to try out FF Quantum (aka FF 57, vanilla, non dev edition) after hearing it repeatedly in /r/rust and hackernews. I was immediately hooked with how fast it is at rendering pages. Now,…
> only to be disappointed and go back to Chrome. Me too. Unfortunately, it seems like Chrome is still wining for me over the new FF. For example, this comments section page takes about 3.5 seconds to load in Chrome and about 7.25 seconds in FF. I run a fair few privacy add-ons in each, so that may not be helping things, but still, a 2x increase in loading for a mostly text comments page is not cool (at least for me).…
(Running Adblock, but that's about it.)