Microsoft has no choice but to make a leap of development faith, by abandoning the IE rendering engine and releasing new WebKit-based desktop and mobile browsers. IE is a dead platform.
Joe Wilcox, Microsoft should dig into the WebKit to stop Google from framing IE (via webkitbits)
Am I alone in thinking this would be a bad thing? We need diversity in our renderers. Right?
(via mikehudack)
Why?
(via zachrose)
Competition. The same reason that we needed Gecko to compete with the IE rendering engine in the first place.
(via mikehudack)
WebKit is Open Source, so I think it is in everyone’s interests to standardize.
(via caterpillarcowboy)
Open source is not an excuse for lack of diversity. Diversity is strength. This applies equally well to our food supply, our genetic pool, our financial system, and Web browsers.
(via mikehudack)
I agree with the principal that diversity is good in general, but there are more factors than simple heterogeneity which create strength or stability in things like our genetic pool or financial system. In the case of speciation, for instance, genetic pools which have undergone a sort of sorting process due to selection pressures also need to undergo a consolidation through reproductive isolation (either due to spatial or biological causes) in order for the process of species formation to occur, the “birth” of a species involves a temporary homogenization of a genetic pool. (Did I get that right, science friends?)
Perhaps a similar process happens here, a process of what Deleuze and DeLanda call “double articulation”: sorting, then consolidation, etc.
(via embody)
I went to go look up “double articulation” on Wikipedia and wound up typing “double science.”
The difference between a rendering engine and the browser itself is not something I totally understand. What I do understand is that when I make something work in any browser besides IE, it will look almost exactly the same in every other non-IE browser. How could this possibly by in Microsoft’s benefit?
