 |
|||||||||
|
|||||||||
|
|
I like it - it's simple and minimalistic, has a small memory footprint and is easy on the CPU. Flash player works fine on my Windows XP box. I'm sure, Mac and Linux version will be available soon too (this is what Sergey Brin has to say ). You may not like the fact that it spawns a new process (23-24Kb) for each opened tab though (on the other hand, it allows you to drag the tabs out of the browser).
Open a couple of tabs and let's count the lines that are "stolen" from the page content: 5 on top and a toolbar at the bottom - total 6. Google Chrome takes away only three lines from the content.
I like the fact that there is no Applet support out of the box. The fact that IE supports Java 1.1 applets out of the box is pretty much useless for most of the cases. Chrome's Help clearly states that it requires Java 6 update 10. If I'd be running Sun Microsystems, I'd invite Google management for a dinner in a very expensive French restaurant. This should be a very happy day for JavaFX folks too - they couldn't even dream of a browser that is forcing people to install the very latest runtime required by JavaFX! Looking forward to seeing a least one example of the JavaFX application that will automatically detect that my PC doesn't have Java 6 Update 10 and will SEAMLESSLY install it in 10-20 seconds.
Here's another interesting twist - I was told that people who are sentenced to use IE because of the corporate policies that don't give you admin rights on your desktop CAN install Chrome. Try it for yourself, but keep quiet.
All these competitive RIA technologies worth nothing if the penetration of the runtime engine is low. Hence having a mechanism of spreading Java runtime for RIA is great for the Java community.
I'm sure, we'll see some quirks in the beta version of Chrome, but Google will iron them out. In a year, Chrome will bite off a decent chunk of the Web browser's market, and as any competition, it's great for us, the consumers.
It looks that Chrome like Safari uses the WebKit or some its variation.
At least, pages that are broken in Safari are broken in Chrome -- and this
is not a WebKit's fault but rather a bad design of site, while WebKit has
~75% conformance to CSS3/CSS2 standards (even better then Gecko, btw)
I am very happy with chrome, the simple looks, small footprint, new
instance with every tab which was a limiting problem when you do parallel
calls from your flex application. I didnt thought of Java update but i
agree this is something quite important for Sun, a company like google
forcing to install their latest runtime.
Well the ironing of quirks issue, actually this is the difference between
Microsoft and Google... Chrome looks like a very complete product which is
labeled as Beta, however silverlight did not even have a button component
so you must do html/js hacks to decorate your silverlight application with
buttons but still it was version 1.1. I am sure soon they will support it
with not only mac/linux but also with a mobile version. Long live google!
Yakov,
@Oleg - the WebKit-based JS engine is faster in Chrome and this is really
good news. But I don't see it as any danger to Flex based RIA.
Any VM is better and more secure than sending and interpreting a source
code in Java Script. Also, these 10-20K of rows have to arrive first to the
client, right? HTTP protocol will remains a bolttleneck regardless of how
fast the data is processed on the client.
Don't forget that Flex has an excellent component and event models, which
make development a lot more productive than JS.
What about security? JS remains vulnarable language.
