3 ms·
Yup. I did some hacking on khtml before Apple's announcement in my attempt to make the early 2000s the year of the Linux desktop. To be fair, every browser engi
by fault1 5y ago
Yup. I did some hacking on khtml before Apple's announcement in my attempt to make the early 2000s the year of the Linux desktop. To be fair, every browser engine was kind of a mess at that time because everyone was trying to reverse engineer IE (or gecko's) undocumented quirks.
The DOM implementation in khtml was particularly well done. I remember one of the major things Apple did was rewrite kjs (into JavaScriptCore), but from what I recall, it wasn't like they did a complete overhaul of khtml right away.
One thing to consider is that Apple, unlike the khtml project, had a lot more power to steer web standards and that tended to clean up browser impls.
It's a shame that Apple decided to have a pretty arcane development process for Webkit, it was not what people expected when they announced Webkit.
- justinator 5y ago> It's a shame that Apple decided to have a pretty arcane development process for Webkit, it was not what people expected when they announced Webkit. This is a fair point. I believe they milked the, "it's Open Source (Come on In!)" and then would periodically release diff blobs and wonder what else the common folk would possibly find wanting.
- VWWHFSfQ 5y agoThis is ultimately why WebKit was forked again into Blink. Because Apple is such a poor steward of open source and WebKit is absolutely riddled with bugs and incomplete implementations of web tech that are pretty much table stakes at this point (WebRTC, among other things). At this point I think most people agree that Safari is the worst mainstream browser in existence. This is why Apple is met with groans instead of praise when their open source contributions come up.