Microsoft wants a monoculture (with Trident) and that's bad.
Microsoft avoids a monoculture (by not using Webkit) and that's bad too
I really pity the Spartan developers. To people like you, there is literally nothing they can do 'right'.
No, you missed my point:
My point was: Sometimes (and this is one, IMHO), "Monocultures" (especially when they involve the implementation of community-agreed-upon "standards" (like approved HTML versions)) are actually HELPFUL to those who Develop against those STANDARDS (and ultimately, to everyone who is "touched" by the implementation thereof.
In other words, I was saying that, since nearly all Browsers are WebKit-based at this point, wouldn't it make sense for any new Browsers (not JUST MS') to throw-in with WebKit (and possibly help improve it along the way!), so that there IS a "monoculture" in this one particular case.
I don't know about you, but if I were a Web Developer I would WANT a "monoculture" when it comes to HTML STANDARDS-Interpretation and Rendering.
For example, how would the internet even exist if various TCP/IP stacks returned different "endian" (or different-length) values in certain "header" fields? Isn't that just a different version of the "My Browser doesn't implement that Tag the same way as your Browser (or doesn't render it at all)" bullshit that drives Web Devs. CA-RAY-ZEE???