Probably not unless someone makes an effort. Understandably there is bad blood between the Epiphany team and Mozilla. For a long time they tried to work with the gecko engine but it kept changing APIs and then Epiphany lost the fight happening in many distributions which decided that Firefox would be the browser of choice. They felt, rightfully so, that Mozilla only cared about their own project and even worse, their own project on Windows.

However late, this is a changing attitude at Mozilla from what I have seen. There are still issues to be resolved as in any complex relationship but at least they are trying to meet us half way. On our part we can not just toss away the support of such a successful project and we do need to also listen to their issues. That is not to say we should not look at alternatives just that we shouldn’t burn bridges along the way.

You seem to be getting defensive. I haven’t even gone into the issue of webkit vs. xulrunner other than stating there is one. The main point was to say I had criticized Mozilla in the past and they came around and really fixed the issues, not just peppered over them. They deserve praise for this as well as all the work they have done for Open Source. Like it or not Mozilla is the most successful Open Source project to date.

Now back to the webkit vs. xulrunner issue. As I indirectly said, competition is a good thing. You yourself are however drawing a line in the sand by reacting to praise of a competitor with a dismissal of the results gathered by the test in question. Sure the data isn’t one to one but it is an independent test that verifies the results that have been coming out of Mozilla itself. Given the claim and verification I can confidently conclude that the Mozilla team is doing a great job pushing performance.

I don’t think I concluded that WebKit sucks so your comment doesn’t reflect much of really what is important to talk about. Please do run those tests and get independent confirmation. Then there is something interesting to talk about instead of reactionary BS that further splits the communities.

Our next cycle should be even better. We’re attacking other areas of performance, will add more developer features and with a focus on mobile + embedding we’ll be closing even more gaps. It’s going to keep getting better.