It's a great browser and I've came back to it even before the changes in Quantum, because the UI is better and it's also a browser I can trust to protect my interests.
Just one thing to consider ... recently in Chrome 66 they introduced the means for cosmetic ads blocking via stylesheets that can no longer be overridden, as Google finally succumbed to demands for it. Firefox has been supporting the feature for years and is on the cutting edge in regards to protecting privacy.
For example I'm using Multi-Account Containers + Facebook Container, an add-on which sandboxes Facebook. Along with the blocking of trackers that's now built-in, Firefox is leading the offense against privacy invading web services (although granted Apple's Safari doesn't do a bad job either).
The only downside of Firefox is that Chrome's dev tools are still better, however Firefox has been improving a lot lately and I'm pretty sure they'll be on par pretty soon. After all, lets not forget that Firebug, which then inspired every other browser, was an add-on that happened for Firefox.
Oh, and I love that they are refactoring its internals via Rust. That's an awesome development.
This is a great point. It's evident in Chrome's course so far that the browser has put Google's interests first, whereas Firefox puts the users' interests first. That's why I stuck with FF when it was slow, and I'm very glad that's all fixed now.
Plus, FF for Android is amazing. I can run Privacy Badger and uBlock Origin on my mobile browser!
Pretty much the only time I use chromium now is when I need to debug Websockets, since the traffic is impossible to see in Firefox. Really hope they fix https://bugzilla.mozilla.org/show_bug.cgi?id=1373639 some day.
On the other hand, Chrome refuses to show binary WebSocket traffic, so I just use SSLKEYLOGFILE + Firefox + Wireshark/tshark to debug secured WS traffic. tshark can even be configured to dump out the packets basically as they come in.
("firefox-bin" on some Linuxes, "/Applications/Firefox.app/Contents/MacOS/firefox" on Mac, etc.). This launches a Profile Manager; pick a profile that isn't being used by any other running Firefox. This avoids accidentally logging keys for normal browsing traffic, making it easier to pick out the target SSL traffic and avoiding a security risk.
Second, launch tcpdump:
tcpdump -i en0 -w dump.pcap
(where en0 is your primary Internet interface).
Browse to the site you want to debug and make some websocket requests.
Finally, you can use tshark to inspect the traffic:
The -e fields I chose there are just examples; this particular example dumps out all the websocket payloads to a file.
You can also configure Wireshark to use the log file, so that you can inspect the traffic interactively; to do so, edit Preferences -> Protocols -> SSL and set the (Pre-)Master Secret key log filename appropriately.
Yep, same here. I use it as my regular browser. Occasionally I switch to Chrome for miscellaneous "other reasons", sometimes just to maintain separation between work and personal browsing sessions (I use FF for work).
I'm about to start a new contract doing React development again though. I wonder if I'll stick to FF or if I'll get dragged back to Chrome for DevTools support...
Typical for me is to have Firefox as a default browser - all links from external apps like email, Slack, etc. is opened there. But when I do web development I open the page I work on in Chrome. When I need to search Stackoverflow or MDN I switch to Firefox.
> Firefox is leading the offense against privacy invading web services (although granted Apple's Safari doesn't do a bad job either).
I thought Safari was leading the charge, so I did a little digging. I haven’t reached a conclusion yet but found out about Firefox’s Tracking Protection[1]. Any idea how it compares to uBlock Origin? If you’re the kind of person that’d rather use as few extensions as possible, would using Firefox’s TP with a solid list be as effective as using uBlock Origin with the same list?
FF devtools also allow you to edit network requests and replay them all in the browser. This was super useful in my QA days as well as for general fun hacking around.
It's a great browser and I've came back to it even before the changes in Quantum, because the UI is better and it's also a browser I can trust to protect my interests.
Just one thing to consider ... recently in Chrome 66 they introduced the means for cosmetic ads blocking via stylesheets that can no longer be overridden, as Google finally succumbed to demands for it. Firefox has been supporting the feature for years and is on the cutting edge in regards to protecting privacy.
For example I'm using Multi-Account Containers + Facebook Container, an add-on which sandboxes Facebook. Along with the blocking of trackers that's now built-in, Firefox is leading the offense against privacy invading web services (although granted Apple's Safari doesn't do a bad job either).
The only downside of Firefox is that Chrome's dev tools are still better, however Firefox has been improving a lot lately and I'm pretty sure they'll be on par pretty soon. After all, lets not forget that Firebug, which then inspired every other browser, was an add-on that happened for Firefox.
Oh, and I love that they are refactoring its internals via Rust. That's an awesome development.