this post was submitted on 16 May 2021
26 points (93.3% liked)
Firefox
18462 readers
80 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is probably not an answer to your question but apple faced such a decision 20 years ago already...and picked khtml/kjs over the firefox engine gecko back then because:
( https://marc.info/?l=kfm-devel&m=104197092318639&w=2 ) (Sorry, it's a long time ago, best post I could still find from that time..but why they picked khtml over gecko was discussed extensively back then)
Of course I have no real clue (and firefox changed the engine in the meantime) but a project based on a portable library in the first place then forked into chrome/blink might have something to do with people finding it easier to integrate in their solutions than an engine specifically written for a single browser.
So the portability is a factor, understood. Thank you for takig the time to answer.
I would say so..but please don't take my word for it. It's really not like I have a clue. It's just what I gathered.