3 ms·
I don't blame them after what Google did with Chrome from all the hard work they poured into WebKit. Especially since they later forked it into a separate proje
by inglor 11y ago
I don't blame them after what Google did with Chrome from all the hard work they poured into WebKit. Especially since they later forked it into a separate project.
So while this is a programming language and such an issue is not likely to rise here - I can see why Apple would be very cautious in this case.
- cromwellian 11y ago1) Forking in open source is not a crime, it is a virtue and fundamental right 2) By "after what Google did with Chrome", do you mean contributing massive amounts of engineering resources to WebKit for several years, exceeding Apple's own WebKit team? Look here: http://www.kaizou.org/2013/04/why-google-dropped-webkit/ http://www.kaizou.org/2013/04/why-google-dropped-webkit/ If someone's forking your project, it's usually because productivity/velocity is going down because of either too much political contention, or too much legacy code.
- inglor 11y agoRight, for the code base it is good - from Apple's PoV however they lost market-share in a billions-of-dollars market
- plorkyeran 11y agoI've never seen any indication that Apple valued their "market share" from Chrome using WebKit in any way, and the people actually working on WebKit for Apple were mostly happy about the fork.
- inglor 11y agoJust as a data point, Google paid Mozilla 300 million dollars two years ago to be the default search provider in Firefox. This is definitely a market.
- s73v3r 11y agoLots of things aren't crimes. Doesn't mean that there might be some ethical questions to it.
- rsynnott 11y agoThe bulk of WebKit is under a liberal license, similar to what they'll likely use for Swift. Google could do exactly the same with Swift if it felt like this (though in practice forking language compilers/runtimes rarely makes that much sense).