Once I saw that my account was linked to Chrome/Chromium without my permission, I cleared everything out of Chrome and stopped using it as a secondary browser. My secondary browser is now a separate Firefox profile:
alias ff='firefox -ProfileManager -no-remote &'It's a huge advantage to be able to pause a script in Chrome, edit the source code, and have those changes injected back into the script. Chrome will even rewind the stack if I edit a line behind where the script currently is.
I use Firefox for all of my personal browsing and for some of my development. But I really miss that feature.
Edit: that and making it easier to debug Node from Firefox. It's still kind of a pain in that area.
[1] https://nodejs.org/api/repl.html
[2] https://nodejs.org/api/debugger.html
[3] https://github.com/epeli/slimux
[4] https://medium.com/actualize-network/a-minimalist-guide-to-t...
Also, Firefox tabs are as ugly as ever (lots of thick lines), and the search bar drop down is cluttered as hell. I thought I’d hate the Chrome 69 tab style, but I got over it in a couple of hours; whereas for Firefox I simply can’t.
[1] https://www.google.com/search?q=hosts+blocklists
[2] https://addons.mozilla.org/en-US/firefox/addon/umatrix/
[3] https://addons.mozilla.org/en-US/firefox/addon/ublock-origin...
I really wanted Firefox to be a replacement for Chrome but it’s so much more sluggish that it’s not even a comparison.
In general I find the UI for manipulating CSS and the DOM easier in Firefox. The Javascript Debugger in Chrome tends to work a little better when jumping in and out of 3rd party libraries, Firefox will just give up trying to break in your code and just dump errors in the console.
Meh... as long as it's not Safari Dev Tools I'm happy.
Thanks!
Not sure if this holds in Linux or Windows.
EDIT: In fact I just noticed that Chrome was outdated. After upgrading it to the latest build, it uses more screen real estate for the UI than FF Quantum's latest build. The difference is even more pronounced if you have bookbar bars turned on.
It's not as pretty or intuitive as Chrome's “shift-click and drag” approach, but it works well enough.
Debugging in Firefox works great!
https://www.jetbrains.com/help/webstorm/debugging-javascript...
Of course now it just seems obvious and I cannot understand what I did earlier.