4 ms·
Why not also throw in libc as well and say it's been over multiple decades?
by statictype 16y ago
Why not also throw in libc as well and say it's been over multiple decades?
- alextgordon 16y agoYes, why not. My point is that Chrome has no clear cut "starting date". It's the culmination of multiple teams over multiple time periods. To compare its progress with IE's over the last two years is a little dishonest, as many of the things that IE is doing now were implemented in WebKit before Chrome's release. It's essentially writing off a huge stretch of time in Chrome's code's history.
- Herring 16y agoMicrosoft is also quite welcome to use webkit. In fact most everyone would be much happier if they did.
- deleted 16y ago[deleted]
- jacquesm 16y agoBecause libc is universal and does not apply to 'just' browsers but webkit does.
- ori_b 16y agoBecause the vast majority of difficulty of developing a browser lies in making it able to display the pages that it's browsing correctly.
- amalcon 16y agoWell, you could, but every browser relies on (some very similar version of) libc. Not every browser relies on WebKit.