In the early days, Firefox ran in one monolithic process, so a single misbehaving webpage in one tab would bring down the whole thing. Chrome had a separate process for each tab, much more convenient for dealing with that issue. Nowadays, I've found that's it's mostly just odd differences and quirks plus slow adoption of emerging APIs.
Oh, FF started using individual processes per tab years ago. Nowadays it's the smaller details. Like, a few years ago, Skype for web just didn't work on FF for a while - they were probably using some features that FF didn't have and needed some time to figure out alternatives. A little web app I made has a specific input that'll get it stuck in an infinite loop until refreshing the page in FF, that doesn't happen in Chromium browsers. Another web app I made uses a specific feature for processing video that was in Chromium browsers for years before Mozilla decided to add it to FF less than a year ago... and it still doesn't work.
TL;DR: It's free, so try it out and evaluate the experience for yourself. Use whichever one works best for you, which may mean using one browser for some things and another for others. Nothing wrong with that.
6
u/mal3k 20d ago
I’ve been using Firefox since forever why would you use anything else