3 ms·
You're right about WebKit's age (and even Trident is just as old as Gecko), although I wasn't aware of the complications of WebKit's embedding API. I wasn't try
by kibwen 15y ago
You're right about WebKit's age (and even Trident is just as old as Gecko), although I wasn't aware of the complications of WebKit's embedding API. I wasn't trying to compare browser engines, but rather to drive home to the parent poster the very sentiment that you express in your final sentence (and set myself up for my own final sentence).
As long as we are comparing browser engines, though, I'd like to stress the relative scarcity of resources available to the Firefox developers. Mozilla's recent windfall with respect to their arrangement with Google is great, but Mozilla's attention is focused on much more than Firefox nowadays--Boot2Gecko, BrowserID, and Rust/Servo being their most prominent diversions at the moment.
- azakai 15y agoI wouldn't say they are diversions, Firefox unsurprisingly gets the vast majority of focus and resources. Today - this wasn't true until recently - I think that Mozilla does have the resources to push additional projects than Firefox.
- Zirro 15y ago"I think that Mozilla does have the resources to push additional projects than Firefox." I wish they would prioritise their UI before they do this, though. Mozilla has one of the most talented UI-teams in the browser landscape based on the mockups I've seen. Take http://blog.stephenhorlander.com http://blog.stephenhorlander.com for example. That looks absolutely amazing, yet I don't believe more than 20% will make it into the final product, since this has been the case before. If Mozilla is prioritizing other things as you mention in another post, it's time to flip those priorities around for a while until they've got what their mockups are showing. Down to the smallest detail.