How about downloading and installing Firefox and seeing if it meets your needs? I totally understand if it doesn't, and then you should keep using chrome or safari or whatever, but I am a back end web dev and Firefox (+ edge) meet all my desktop needs.
Give it a try, you might like it.
And that'll have a lot more impact than testing cross browser regularly.
At my work I only work in Firefox, another Dev only works in Chrome, etc. By each developer only working in one browser all the time we get pretty good cross browser testing. This has led me to only using Firefox at home too since it works really really well.
Same here. When I joined my current team, I was told I should use Chrome, because nobody really tested the site on Firefox, so there may be some breakage. That made me double-down on Firefox use, just so that I could report if any problem actually occurs.
> And that'll have a lot more impact than testing cross browser regularly.
That depends entire on what you mean with "impact" here.
One site that does not work on Firefox has a great impact too. When that "one site" becomes every fourth site, then "we", the webdevelopers have handed Chrome their monopoly.
> That depends entire on what you mean with "impact" here.
Fair enough. I meant that using Firefox regularly as a web developer would have a larger impact on keeping the web free than testing periodically on Firefox. Why? Because testing periodically won't exercise the browser quirks as thoroughly as every day use (and sometimes time intensive cross browser testing gets sacrificed to schedule concerns). There's also an additional bonus of keeping browser share up, but that's not the primary benefit in my mind.
Give it a try, you might like it.
And that'll have a lot more impact than testing cross browser regularly.