Well, I for one am glad that Microsoft decided against WebKit/Blink.
Because of its popularity as a rendering engine, being used by Safari, Chrome and Opera, both on the desktop and on mobile phones, it is quickly becoming a monoculture. Even if we are talking about an open-source project, to me it smells too much like the lock-in that IExplorer once had on the market and people might not remember, but IExplorer was at some point very innovative and the best browser available. And many people also don't remember what happened after that.
So even though I'm very grateful about WebKit/Blink, we really must avoid repeating mistakes of the past. Multiple implementations of a standard are very healthy, monocultures are not.
However, I also think that given this overhaul, Microsoft should open-source this rendering engine. I really hope they do it and it would be in their interest to do so.
Comments
Well, I for one am glad that Microsoft decided against WebKit/Blink.
Because of its popularity as a rendering engine, being used by Safari, Chrome and Opera, both on the desktop and on mobile phones, it is quickly becoming a monoculture. Even if we are talking about an open-source project, to me it smells too much like the lock-in that IExplorer once had on the market and people might not remember, but IExplorer was at some point very innovative and the best browser available. And many people also don't remember what happened after that.
So even though I'm very grateful about WebKit/Blink, we really must avoid repeating mistakes of the past. Multiple implementations of a standard are very healthy, monocultures are not.
However, I also think that given this overhaul, Microsoft should open-source this rendering engine. I really hope they do it and it would be in their interest to do so.