Mac Chrome Lead Rationalizes Early Release, Needs Your Help
For the past several months, everyone has been bitching about the lack of availability of Chrome on the Mac. So Google did something about it, and formally released a developer build to the public, making sure to note that it wasn’t really ready for prime-time. Nevertheless, a ton of people downloaded it and then started bitching that it wasn’t ready for prime-time. So today, the lead engineer on Chrome for the Mac took some time to respond to the critics.
“What was the point of releasing at this stage, you might ask? It’s clearly not finished. Clearly. It’s missing a large number of features, some half implemented, others not at all. Why even bother? Doesn’t it just make us look bad?,” Mike Pinkerton (also the man who leads the Camino browser development team for Mozilla) writes today. His answer is basically that they don’t care how it makes them look to release an unfinished product. Part of the development cycle of open source software is to get it in the hands of outside developers and have them help in completing the product.
Check also related entries:
- Some Early Pictures Of Chrome’s New Web Apps Feature
- TechCrunch Giveaway: Five Google Chrome Cr-48 Notebooks
- The Version Number Is Dead. Google Barely Whispers The Launch Of Chrome 8
- Google VP: Chrome OS Coming To Tablets & TVs; Windows And Sys Admins Going Down
- First Piece of Mozilla’s Web Apps Project Arrives, But Can it Outfox Chrome?