2 ms·
Understand all and Aaron, at the question: "You guys forked webkit which forked khtml, so you all had a nice leg up no?" says: "Yes. Just like IE started fro
by twsted 4y ago
Understand all and Aaron, at the question:
"You guys forked webkit which forked khtml, so you all had a nice leg up no?"
says:
"Yes. Just like IE started from Mosaic Spyglass. But a rendering engine (like WebKit/Spyglass) is not a browser. Certainly not a multi process, sandboxed browser. Chrome v1 was a 200 person year effort."
but, come on, much work was already done and they seem not to remember this.
- doctor_eval 4y agoAlso, Chrome was using WebKit long before they forked it. IIRC, for several years they used the exact same engine used by Safari, and both Apple and Google were contributing to it.
- zaphar 4y agoNo where in that thread is he suggesting they weren't standing on the shoulders of those who came before, but he's also right a rendering engine is not a browser and at the time Chrome was revolutionary in a number of ways. It was crazy fast. Even compared to other khtml browsers. It's multi-process architecture meant that for the first time a single page or tab couldn't take down your whole browser. And yes that was something I experienced frequently at the time. 200 person years to deliver a full browser that was an leap forward compared to the rest of the browsers is seriously impressive. His point stands they did it without a death march.