While I agree with most of Jeff's sentiments - I do have to diverge on marking how fast software moves by something as arbitrary as a version number. Something such as versioning is completely ad-hoc and should not mark the advancement/maturity of a software product. How long did VLC take to get to version 1.0? That does not mean their development/release cycle is any slower than Chrome's. Perhaps I am being a bit drastic here, but it appears to me that judging software iteration speed by a version number is almost as lame as marking a programmer's efficiency by the number of lines of code he writes in a business day.
That jumped out at me also as a completely wrong-headed statement. To paraphrase Newton, they were standing on the shoulders of giants when they started.
I'd take issue with his other premise as well. Though I suspect he's on a different operating system, Chrome on Mac OS 10.5 seems to be an insufferable memory hog.
Chrome was built for Windows. Mac OS X was not supported until Version 5. Why use Chrome on Mac OS X when there's another good Webkit browser there by default?
"Good" is relative. Compared to IE 6, Safari for Mac is great. Compared to Chrome, Safari is annoyingly slow. Chrome never just locks up the way Safari does.
Re:Go That Way, Really Fast
by statictype on Sunday September 12, 2010 @09:01AM
(#1683580)
Why not also throw in libc as well and say it's been over multiple decades?
Re:Go That Way, Really Fast
by alextgordon on Sunday September 12, 2010 @09:28AM
(#1683619)
Yes, 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.
Microsoft is also quite welcome to use webkit. In fact most everyone would be much happier if they did.
Because libc is universal and does not apply to 'just' browsers but webkit does.
Because the vast majority of difficulty of developing a browser lies in making it able to display the pages that it's browsing correctly.
That's obviously wrong. The Chrome beta was over two years ago, and you can bet V8 didn't just appear overnight. Chrome is older than its 1.0. Not to mention that it's based on WebKit, which has been in development for a decade (if you start from KHTML).