tk, 7 hours ago to apple Most Web-savvy folks know that Chrome’s lineage can be traced back to Safari (WebKit, etc.), and be traced further back to KDE’s Konquerer (KHTML, etc.). But did you know that Apple was also considering Mozilla’s Gecko engine as the basis back when planning development of Safari? KHTML was chosen because the codebase was significantly cleaner than the XPCOM bloat in Gecko. (That name still strikes fear in me to this day. :blobfoxscared: ) Interestingly, the Gecko codebase has been since cleaned up significantly. That means that, if things had gone differently, Gecko could’ve ended up as the browser engine that rules the world today. :blobfoxgoogly: #Apple #Safari #Google #Chrome #Mozilla #Firefox #Web #webdev
Most Web-savvy folks know that Chrome’s lineage can be traced back to Safari (WebKit, etc.), and be traced further back to KDE’s Konquerer (KHTML, etc.).
But did you know that Apple was also considering Mozilla’s Gecko engine as the basis back when planning development of Safari? KHTML was chosen because the codebase was significantly cleaner than the XPCOM bloat in Gecko. (That name still strikes fear in me to this day. :blobfoxscared: ) Interestingly, the Gecko codebase has been since cleaned up significantly.
That means that, if things had gone differently, Gecko could’ve ended up as the browser engine that rules the world today. :blobfoxgoogly:
#Apple #Safari #Google #Chrome #Mozilla #Firefox #Web #webdev