LATEST CHATTY HEADER
Subscribe to Shacknews Mercury starting at $1/month!
Chrome Shack Community Guidelines Chatty Search
Scroll down to join the conversation.
New to Shacknews? Signup for a Free Account
Already have an account? Login Now
Subscribe to Shacknews Mercury starting at $1/month!
Chrome Shack Community Guidelines Chatty Search
Scroll down to join the conversation.
Thread Truncated. Click to see all 126 replies.
Any coder can probably tell you what the result is when you take a poor initial design, and then layer more than a decade of maintenance work on top. When we conceived Chrome we explicitly chose to use WebKit instead of Gecko, even though all of us were Gecko hackers, because we believed it would be easier to make WebKit (which was already very fast) compatible with the web at large than to make Gecko (which was already very compatible) fast.
There have been a number of Mozilla hackers over the years with exceptional ability, such as L. David Baron, Boris Zbarsky, and Robert O'Callahan, who have managed to slowly redesign the underpinnings of Gecko to get rid of a lot of the bad ideas and replace them with good ones. Sadly, they're hampered by having to take the airplane apart and re-build it while it's in flight. This is extremely difficult.
The post has been reported. Thank you!
You must be logged in to post.
You must be logged in to post.