4 ms·
Alex Russell has a good analysis about the move: http://infrequently.org/2013/04/probably-wrong/ http://infrequently.org/2013/04/probably-wrong/
by mythz 14y ago
Alex Russell has a good analysis about the move:
http://infrequently.org/2013/04/probably-wrong/ http://infrequently.org/2013/04/probably-wrong/
- marshray 14y agoThat (and the linked article) was the nicest "fork you" I've ever read. These developers have class.
- macrael 14y agoThe argument is essentially: "It took up lots of engineering time and effort to maintain compatibility with other platforms, so this allows us not to worry about other platforms and only focus on our own and that will allow us to move faster." Hopefully this is easier for everyone. If the chrome multithreading architecture really was the pain point then does that mean that webkit will also be deleting thousands of files and become easier to build, just as the chrome team is removing compatibility for other webkit targets? Or will WebKit remain the mess it is now because it strives to work on all the other platforms? What if Apple decided to do the same thing? WebKit is this wonderful open source success story in part because it runs in so many places on so many things, but isn't a large part of that only enabled because the main contributors took the time to make sure that their work continued to run on the various different architectures? Will Google turn away patches that enable Blink to be compatible with platforms not their own? This is an interesting move.
- cromwellian 14y agoDoes Apple already maintain a private WebKit fork for iOS?
- makomk 14y agoI think Apple has already made a similar decision. A while ago, they decided that they'd allow commits which broke the build on non-Apple platforms and that it would be up to platform maintainers to try and keep up.
- deleted 14y ago[deleted]
- alexchamberlain 14y ago*multiprocess