I recently made Safari my default browser for this reason. If Firefox’s days are numbered, I figured I’d get ahead of it than be forced. Ublock origin isn’t available for safari, but I was able to use the same content blocker that I use on iOS and it seems to be doing the job.
IMO We have at least a year of runway with FF. The decision from the judge on what Google will have to do is not expected until mid-2025, and surely Google will appeal the judgement. So I don't want to give the impression that FF is right on the brink of death, just that as a user of FF, I am pretty worried about the road ahead for FF/Moz.
Which is why personally I'll probably stick with FF until the bitter end.
I just hope that Moz/FF can pull a rabbit out of the hat, because (imo) atm things ain't looking good for the long term future.
I find I am enjoying the syncing features of Safari (and iOS), and it's much less resource intensive on my 2019 MacBook Pro. Also, Safari seems to be the most fiddly when it comes to websites (either because it's stricter in some cases or has strange bugs in others), so I find I am catching more issues for web dev by using it.
Right on with safari not being used by webdevs. Safari is still my browser of choice when I want to hand someone my laptop for some purpose (like ordering food) and not have them complain about my tree style tabs. Some websites they clearly don’t test at all with safari. Big client websites too like tacobell.com, no safari testing at all. Menu images rendered with extra inch wide margins for some reason along with the usual broken fonts.
Weird, next week will complete 21 years of my exclusively using Safari on the desktop, and I’ve yet to notice anything like this. Admittedly I’m not ordering from Taco Bell, but sites being unusably broken is simply a non-issue for me.
