You get used to it - UI is slightly different in some areas, but it lacks for no major features and performance is good, like firefox in general.

I've found it's extremely valuable to be developing sites in Firefox using the dev tools simply to help catch issues that the rest of the team ignores as they're all stuck on Chrome. Fights monocultures by default!

I think Firefox is better in some areas, especially their CSS grid viewer. https://developer.mozilla.org/en-US/docs/Tools/Page_Inspecto... I'm also keen to checkout the new Replay feature. https://developer.mozilla.org/en-US/docs/Mozilla/Projects/We...

Better in some aspects, worse in others, the interface is different enough to create a bit of a transition barrier.

You won't be worse off, it isn't a big effort to get used to FF devtools, but you must accept a learning curve if you want to switch.

Sadly, the performance inspector is still pretty useless compared to what Chromium is offering.

I’m a Firefox ddg user, and I would recommend Chrome for devtools still. As of last month, Firefox devtools didnt even recognize meta viewport tags which caused UI discrepancies between testing and production. Chrome devtools does have it.

That being said, I still switched back to Firefox and ddg after I close devtools.

In Chrome 79 they broke or removed hovering over variables. They say it will be fixed in Chrome 80. https://support.google.com/chrome/thread/22882968?hl=en

I use Firefox as my default browser. But the dev tools is too slow, apparently someone thought it was a good idea to rewrite it in React, causing it to lag even on a few thousand console log messages on a fairly powerful workstation. And there is no search functionality, only filter. So I've started to prefix all my debug messages with whatever I'm working on just so that the logs can be found in the Firefox dev tools console. One good feature though is that you can filter on type of messages, like only show error messages, or warnings. Which is very annoying in Chrome dev tools where it will tell you there is an error, but you can't click on it, so there is no way to see the actual error.

I’ve always preferred Firefox’s dev tools compared to Chrome’s.

Really like the ability to outline flexbox and grid elements.

I am not OP but I'm a FF user. I haven't got around to learning FF's dev tools and still need Chrome(ium) to test that platform for compat anyway. So I just still use Chrome dev tools (which also work for NodeJS instances) but use FF for actual browsing.

I like Edit and resend in the Network tab. I don't know how to do that in Chromium.

Firefox has a great feature where live css changes are placed into a "diff" panel.

Rather than having to remember all the small changes you made, you can just copy and paste the script out (or even just view what you changed).

When I’m using the Chrome tools, I miss some FF features, when I use the FF tools, I miss some Chrome features.

I generally like the FF tools better nowadays, but Chrome’s are a bit faster.

I heard FF recently added WebSocket support to their dev tools (being able to see payloads). Been meaning to give it another try.

Re:qwant

France has a more permissive surveillance regime than the US[0], and as a foreign (US) user I have no recourse if they spy on me.

Furthermore, here are some quotes from qwant:

>We do not use any cookies or other advertising tracers to create your profile for commercial purposes. This means that you can use Qwant with confidence, we will never try to establish your psychological or commercial profile to sell it to third parties, here or elsewhere. [1]

Note the "for commercial purposes" in the first sentence, and the "to sell it to third parties" in the second. These are weasel clauses.

[0] https://www.theguardian.com/world/2015/jul/24/france-big-bro...

[1] https://betterweb.qwant.com/5-reasons-to-be-brave-and-choose...

Qwant doesn't work for me at all on Firefox. It displays an empty page. Does anyone else have that problem?

In the console I get a warning and an error:

> Content Security Policy: Couldn’t process unknown directive ‘script-src-elem’

> TypeError: browserLanguage is undefined

All of these are using Bing results, right?

Startpage was good but I think they were recently bought out by a less than a good party

wow, those seem quite fantastic at first glance. If I search for my real name I get every single profile I've ever created since the beginning of time - as opposed to google listing a bunch of random garbage. Names there are like John Doe returns famous people named John OR Doe above the person(s) with the actual name.

EDIT: I right click the search box and make qw and sw keywords for them.

EDIT2: I'm just looking for a functional google alternative.

I tried Swiss Cows just now, it appears effective at first glance but a little longer and realized I’ve never seen a more sanitized and curated search.

I don’t necessarily mean that good or bad. Just interesting how... different it is. Seems good if you know your thug exists already and someone approved it for their results.

"swiss cows"... .ch right

Qwant was proprietary last time I checked and didn't seem that privacy centered as they say

Also >France

Yeah I'm still a little pissed about not getting the green bar for payments (and definitely about not being able to see 'https' to verify it).

What's the story with Chrome messing up URLs? I missed that one...

The problem is it's impossible to separate "this changed it sucks" from "this is actually bad" since the messages are always the same. E.g. in this case you didn't even bother explaining why the new way works worse for you you just said "it changed, I left! Make note!" and I mean that's fine if that's what you actually wanted them to make note of but no company with competition is just going to keep every workflow the same for over a decade and wait for someone else to come out with a better product to replace them.

Firefox is definitely an amazing experience, especially if you use Firefox Containers[1]. My only gripe is that the UX of containers isn't quite ready for prime time yet (e.g. your container setup doesn't sync by default).

And there really needs to be an easy way to switch profiles. Firefox has had profiles for basically forever, but it's much easier to switch profiles in Chrome.

[1] https://support.mozilla.org/en-US/kb/containers

Firefox preview is fantastic. I started using it expecting a very unstable experience and... it hasn't been.

For me its been fantastic.

What was the ublock fiasco?

As a Mac/iPhone user the only thing that sort of breaks seamless is that Apple doesn't allow you to define a custom default browser on iPhone.

I have Firefox in the dock on iPhone and it's really great but random links, e.g. via messaging, get opened by Safari first.

Changed ownership:

https://news.ycombinator.com/item?id=21371577

You can get some extra speed by forcing GPU rendering

https://news.ycombinator.com/item?id=21945206

It is not 100% bug free yet, though