Re: OK, but what now?
someone could take-up the Firefox source code and improve on it
I'd love to but for the code-bloat. It would take YEARS to figure out how the damn thing works! This is the BIGGEST PROBLEM
And web sites seem to be DROPPING COMPATIBILITY - NOT EVEN MY BANK will accept a Firefox browser, at least NOT on their "new" *a year old) web site, for some reason (probably web-side ARROGANCE). Everything on that site fails to work with FF, starting at the logon page.
More and more web-side enshittification as well, it seems. DELIBERATE FF INCOMPATIBILITY???
I would think that Apple might have an interest in WebKit being at the cutting edge of compatibility though, and chances of "web developers" RESPECTING iPhone and Mac are a bit higher.
[I cannot believe I said "web developers" - now I need mouthwash to kill the bile taste]
NOTE: FF totally blows it with the CONSTANT need to "update". slack, github, others FREQUENTLY 'complain' at you if you';re NOT using "the latest bleeding edge" features on the scripting side, and often LOOK LIKE CRAP or just FAIL TO OPERATE without "up"grading your perfectly good setup. Updating FreeBSD [on a dedicated developer system like mine where I guild from source fo max stability] take DAYS and generally must "update EVERYTHING" then deal with WHAT BROKE **THIS** TIME. Stinks on ice! I'd rather fix it ALL then stay STABLE for YEARS.
WHY is this? Is it Google-monster's way of DRIVING EVERY OTHER POSSIBLE COMPETITOR AWAY????
This is why 'web kit' makes more sense, because as a separate entity, it can service more browser front-ends as long as they do NOT change the ABI/API in the process. And an 'Open' version could be SPY/ENCUMBERANCE-FREE, allowing as-block etc. to work as desired.
[Things Mozilla wasted effort on instead of polishing the rendering engine with minimal tweeks and efficiency improvements - the list must be ENDLESS!!!]