Google Chrome
Google Chrome is finally here. This kinda reminds me the old days where you’d have to pick who’s side you were on – Netscape or Explorer… At least now the rendering issues are obsolete, and the browsers are competing for functionality and ease of use, both of which are celebrated in this new browser.
ABOUT THE AUTHOR(S)
Constantinos is employed as a Creative Director for Tribal DDB Athens. In his ever dwindling spare time he works on the development of UX Magazine and Joblet. You can find out more about him here of follow him on twitter.
Add new comment
Comments
Great article, very well written and some nice insights in there. Personally I feel that the iPad will lead the way to slightly more targetted devices for individual sectors of business; in the food industry a thinner (width wise) devise would bridge the iPhone/iPad gap. Others will produce for this in time, think about how many mobile phones try recreate the iPhone app or touch screen experience.
Incredible speed. I was expecting good performance but nowhere that good. It’s insane. Webkit with it’s great standards support making inroads in so many fronts ( AIR, iPhone, Android and now Chrome ) is great for web standards and the Web in general.
Since when have rendering issues become obsolete? A lot of people still spend a lot of time tweaking their code to work with every browser. And based on some quick testing, Chrome has its own idiosyncrasies that we’ll have to code for now too. I will give it credit for being fast, but it’s got a serious lack of functionality and questionable usability benefits. It would be totally ignored if anyone but Google were releasing it. But it’s got potential…
@Ron
You’re right. But I didn’t really mean obsolete-obsolete, rather than a more streamlined environment for us to work in. It’s much less hassle to markup a site today than it was back in the days.
For me, most of the “issues” that arise in various browsers are commonplace, and I just write up the CSS code before I even test a site. 99% of the time, I’m good to go.
So, as it may seem, rendering issues are there, but it’s much easier to tackle.
That is what I meant to write, in so many words :)
i’m willing to try it out just to see if it works more efficiently than FireFox… if it’s faster than Firefox and isn’t IE, then i’ll use it
Incredible speed. Wicked fast. Comfortably stable. What I like about it best is that it’s stripped down — there’s not a lot extra on the UI, which allows more browsing area.
Incredible speed. Wicked fast. Comfortably stable. What I like about it best is that it’s stripped down — there’s not a lot extra on the UI, which allows more browsing area.
i’m willing to try it out just to see if it works more efficiently than FireFox… if it’s faster than Firefox and isn’t IE, then i’ll use it
@Ron
You’re right. But I didn’t really mean obsolete-obsolete, rather than a more streamlined environment for us to work in. It’s much less hassle to markup a site today than it was back in the days.
For me, most of the “issues” that arise in various browsers are commonplace, and I just write up the CSS code before I even test a site. 99% of the time, I’m good to go.
So, as it may seem, rendering issues are there, but it’s much easier to tackle.
That is what I meant to write, in so many words :)
Since when have rendering issues become obsolete? A lot of people still spend a lot of time tweaking their code to work with every browser. And based on some quick testing, Chrome has its own idiosyncrasies that we’ll have to code for now too. I will give it credit for being fast, but it’s got a serious lack of functionality and questionable usability benefits. It would be totally ignored if anyone but Google were releasing it. But it’s got potential…
