This really isn't an accurate representation of what happened. WebKit's success didn't happen overnight, and people weren't jumping on it from the get-go. In fa

This really isn't an accurate representation of what happened. WebKit's success didn't happen overnight, and people weren't jumping on it from the get-go. In fact, there was a long period of people using Gecko and engineering their own embedding/browser solutions because it was widely, and correctly realised that Gecko was a more mature and featureful engine. This was my job for several years before I was employed by Mozilla (and indeed, I did do some WebKit work at the time too - but there was far less demand for it). It was only through a long period of neglecting these users that WebKit was allowed to mature and become successful. There was a good reason for doing this (see yoric's blog post, linked in my other comment above), but I think we've past the time now where we need to reconsider this direction somewhat.