It seems to still be in "rumor mode", but the "secret" documentation is compelling.
Comics book pages tell the story of Google Chrome, which seems to me more like a networked-based application software development kit than a browser, but isn't that what a browser is anyway?
While many web pages are just that, pages, many more are real applications, software if you will. As a web-based applications developer myself, I am often frustrated by the constraints of browsers. I used to offload some of the more intricate components of the user interface to Adobe's Flash platform, using the open source ming project, but Adobe's (like Macromedia before it) closed-source, proprietary methods kept bugging me, until I instead embraced AJAX.
Why is it still such a challenge? Well you've got so many different clients, its very challenging to deliver a consistent experience. Firefox has helped, but there are still so many people using Internet Explorer, the browser which must pledge allegiance to Microsoft above all else. Therefore, when it comes to working with standards that cross the divides into open source realms, like linux and FreeBSD, its not such a smooth ride.
Right now there are two big, viable, open source web browser projects - Firefox and WebKit (powers Safari and Epiphany), and I really hope we see a lot more. There are many smaller open source web browser projects too, let's hope they stick around and serve the niche needs of all the various computer users out there.
How would Chrome do things differently than Firefox or WebKit? Or an even better question, how much differently can they do things without breaking interoperability with existing standards?
UPDATE: Apple Insider says its based upon WebKit, but I keep reading elsewhere (and in the comics) that its built "from scratch".
Comics book pages tell the story of Google Chrome, which seems to me more like a networked-based application software development kit than a browser, but isn't that what a browser is anyway?
While many web pages are just that, pages, many more are real applications, software if you will. As a web-based applications developer myself, I am often frustrated by the constraints of browsers. I used to offload some of the more intricate components of the user interface to Adobe's Flash platform, using the open source ming project, but Adobe's (like Macromedia before it) closed-source, proprietary methods kept bugging me, until I instead embraced AJAX.
Why is it still such a challenge? Well you've got so many different clients, its very challenging to deliver a consistent experience. Firefox has helped, but there are still so many people using Internet Explorer, the browser which must pledge allegiance to Microsoft above all else. Therefore, when it comes to working with standards that cross the divides into open source realms, like linux and FreeBSD, its not such a smooth ride.
Right now there are two big, viable, open source web browser projects - Firefox and WebKit (powers Safari and Epiphany), and I really hope we see a lot more. There are many smaller open source web browser projects too, let's hope they stick around and serve the niche needs of all the various computer users out there.
How would Chrome do things differently than Firefox or WebKit? Or an even better question, how much differently can they do things without breaking interoperability with existing standards?
UPDATE: Apple Insider says its based upon WebKit, but I keep reading elsewhere (and in the comics) that its built "from scratch".
