16 ms·
> In short, most webkit devs are happy about this. It's worked out well for everyone. I can't say the same about front-end web devs. They are potentially looki
by geoka9 14y ago
> In short, most webkit devs are happy about this. It's worked out well for everyone.
I can't say the same about front-end web devs. They are potentially looking at yet another browser family that can have its own quirks (sure, safari and chrome were different enough already, but this fork means that now they can be different at a lower level).
- chc 14y agoI believe this is pretty much the definition of "fear, uncertainty and doubt." Let's not spread it around. Google already basically ran their own fork of WebKit — it most definitely was not the same codebase in Chrome and Safari. Now they've just made it a clean, official one. Let's not freak out about problems that may never exist and certainly don't yet.
- tambourine_man 14y agoThey shared WebCore: pretty much all of HTML, CSS and JS parsing and CSS positioning. That's most of what a front-end, PSD2HTML kind of developer has to worry about. So yeah, they will probably differentiate even more now.
- schrodinger 14y agoI don't think it will be that bad. WebKit is already pretty well established, when they're this far along I doubt they'll diverge much. For the most part, even Firefox and WebKit render the same, even though they have no common lineage. This isn't going to be like IE6 vs Firefox.
- anthonyb 14y agoThe Law of conservation of complexity in action! :)
- cheald 14y agoOn mobile at least, Safari is already effectively its own browser family. Even though it's webkit-based, it has a huge range of quirks and caveats that don't apply to its desktop brother. Nothing really new here. What we will hopefully get is greater parity between desktop and mobile Chrome versions (which is already quite good), which I think will end up being an overall win.