I installed Chrome on day one – I’ve always prided myself with being on the bleeding edge and with web browsers it is no different – I had the RCs of Firefox three before they were fully released and Chrome was no different.

I have to admit though that I’ve just clicked the button on making Firefox my default browser again – Chrome is just too buggy.

It’s an interesting case of chicken and egg – is it the fault of non-compliant websites that they don’t render nicely in Chrome? Or is it a failing of the browser itself?

Either way there was just too much that didn’t work. I love Chrome – it’s quick, it’s mighty purty and it’s Google – the triumvirate that normally guarantees success – but in this case I’m afraid I’ll have to take a watching brief and come back to it once wither it works right, or most websites work right with it.

Ben Kepes

Ben Kepes is a technology evangelist, an investor, a commentator and a business adviser. Ben covers the convergence of technology, mobile, ubiquity and agility, all enabled by the Cloud. His areas of interest extend to enterprise software, software integration, financial/accounting software, platforms and infrastructure as well as articulating technology simply for everyday users.

  • I’ve been playing around with Chrome too. Interestingly our site, which is not exactly simple on the code side, seems to run well in Chrome even though we never tested it until Chrome released. My CEO did a little post about how LiquidPlanner runs in Chrome.

    I’m very interested because Chrome is Google’s foray into building a browser specifically for running web applications. Being a SaaS company with a rather javascript intensive product this piques out interest to say the least.

    The chicken & egg problem of getting enough Chrome users to justify supporting Chrome on your site will diminish over time I think. The proliferation of (relatively) standards compliant browsers makes it less important to support any ONE browser and more important to support the standards.

    That’s my take. FWIW I too have switched back to FF3.

  • “…is it the fault of non-compliant websites that they don’t render nicely in Chrome?”

    In what sense are you using the word “non-compliant”?

  • my question is…

    does chrome use standards based rendering and if so is the issue in poor site coding. Or is chrome doing something with compliantly coded site

    I’m not passing judgement on the cause – merely saying that from a user perspective it’s not there yet

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.