3 ms·
Back in 2011, I got my first exposure to WebKit and OSS in general as I was hanging out at my friend's office in downtown MV, 9pm on some random weekday. I rec
by hkmurakami 14y ago
Back in 2011, I got my first exposure to WebKit and OSS in general as I was hanging out at my friend's office in downtown MV, 9pm on some random weekday.
I recall him working on submitting a patch (which I think got accepted after a few necessary revisions) to WebKit, and him explaining to me how WebKit is behind both Safari and Chrome, and how even though the companies and its fanboys are grabbing at each others' throats, the developers are happily working together, conversing casually on the mailing list and on twitter. It reminded me of the great sports rivalries, where the fans and media rile up the heat and hatred, but the players themselves remain respectful to their brethren on the other side of the lines.
In the years since, I've been able to help out some OSS projects as a non-coder, and I look back and think that learning about the collaboration behind WebKit certainly nudged me a little bit towards this direction.
It's a bit sad for me to see the Google and Apple teams split in this manner, since it was such a visible and prominent example of how OSS can bridge corporate divides, but I am hopeful that down the line we'll all look back at this moment in history with fondness.
- general_failure 14y agoThere's nothing to be sad about. Some people seem to think this is some sort of tragedy and failure of webkit the opensource project. It's not. The fork happenned to a large extent for a want of control on the code base. So, it's mostly technical. WebKit has atleast 8 ports in trunk. Every part of it - networking, os, javascript engine, bindings, plugins, graphics has been hacked to death. And it has abstractions galore. Now imagine you worked for WebKit. If you wanted to commit something, you had to test it against 8 ports. Many of these ports are cross platform. So, you are really talking about like gazillion combinations (mac, windows, linux, retina vs non-retina, os versions). It was not a happy place to develop and everyone in the project recognized this. The pace of development was getting very slow because of the above. Apple faced this and said WebKit2 is all theirs and nobody else should really use it. Google faced this and decided to fork. In short, most webkit devs are happy about this. It's worked out well for everyone.
- macrael 14y agoWhat about the ports? They seem to have lost out
- 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! :)