Category Archives: google

Google Chrome for Mac and Linux will be a long while coming

When I looked at the Chromium source code and did a build, I noticed how much of it was Windows-specific. Although the WebKit rendering component is already cross-platform, it seems that the Mac and Linux versions of Chromium and therefore Chrome are a long way from ready. This is from the build notes for Mac OS X:

Right now, the Mac build is a work in progress that is much closer to the start than the finish. No application that renders web pages is generated at the end of these instructions!

Cross-platform work usually involves compromises, and it looks like the Google team pointed the dial more towards optimising for Windows than towards ease of porting. That surprises me, since it likely means more work maintaining the application for several platforms as well as delays now.

Chrome’s ambitions as an application platform cannot be realised until it runs on the Mac. Further, a disproportionate number of web designers and developers use Apple.

How long is a long while? Good question. I’ll be seeing some Google folk tomorrow; I’ll let you know what they say.

Technorati tags: , , , ,

Defining cloud computing

I liked this post by Larry Dignan on the cloud computing buzzword and how meaningless it has become.

Writing on the subject recently, I was struck by the gulf between what some people mean – online apps like Google Apps and Gmail – and what others mean, on-demand utility computing such as that delivered by Amazon Elastic Compute Cloud or Flexiscale. These things have little in common.

Dignan has even more examples.

Should we abandon the term? Maybe, but I find it useful if only as shorthand for describing how the centre of gravity is shifting to the Internet.

Some services are more cloudy than others. Dignan refers to this Forrester report (though you’ll have to look at the blog post for the extracts, unless you want to buy it) which has a table of “six key characteristics.” I don’t agree with all of them; the business model, for example, is not an inherent part of cloud computing. I am interested in number two:

Accessible via Internet protocols from any computer

Any computer? OK, probably not the Atari ST which I have in the loft. Any computer with a web browser? What about requiring a “modern” web browser, is that OK? Java? Flash? Silverlight? A specific version of Java or Flash? What about when we need a runtime like Adobe AIR or Microsoft Live Mesh? What if it doesn’t run on Linux? Or on an Apple iPhone? What about when there is an offline component such as Google Gears? All these things narrow what is meant by “any computer”.

This is the old “rich versus reach” debate; it is still being played out. My point: cloud computing isn’t a boolean characteristic, but a continuum from very cloudy (NTP) to not cloudy at all (Microsoft Office).

What does not a valid win32 application mean? Say, with Chrome setup?

Browsing through my logs I see a ton of searches like this:

chrome setup.exe not valid win32

I’m not sure which part of this site they are hitting. Anyway, this is for you.

In my experience “not a valid win32 application” invariably means a corrupt executable. I’d guess that what has happened here is that your web browser did not download the entire setup file, but stopped half way. Internet Explorer is particularly bad in this respect: it tells you that a download is complete, when you can see that it is not because the download size is not what it should be. It usually happens when the connection is poor, either at your end, or because of a busy server. It beats me why browsers don’t make a basic check on the file size after download.

It can also happen with a CD or DVD install, if the disk is corrupt or the drive is failing; or if your hard drive is failing.

The usual solution is to re-download the file.

Technorati tags: , , ,

What happens to the browser market when Google plays the OEM card?

Here’s a bit of speculation. My initial thinking about Google Chrome was that it would mainly take market share from Firefox; and that while IE’s share may continue to erode, Chrome is unlikely to accelerate that much.

I’m beginning to change my mind. One factor is OEM installs. We all know what a huge influence default installs have on users, which is why software vendors are happy to pay the likes of Dell and HP for space on the desktop, or to be the default anti-virus engine, for example. This has often been to the detriment of the user’s experience overall, to the extent that it helped to damage Vista’s reputation, but that is an aside.

Now, one thing I’ve noticed is that Google’s toolbar often turns up by default in OEM installs of Windows. When you start up for the first time (or the first time for real, after all those reboots), IE confronts you with Google’s terms of service. However, I have not yet seen Firefox installed as the default web browser. I’ve presumed that Mozilla doesn’t quite have the financial muscle to do it, or maybe there are other reasons.

Google is a more formidable presence than Mozilla. What if Google buys browser share by being the default browser on machines from the leading OEMs? I suspect that would soon impact IE’s share. Microsoft cannot prevent it because of anti-trust constraints.

Since Chrome is in effect the new Google toolbar, this move strikes me as inevitable.

This would mainly impact the consumer and small business space. IE has some special advantages for enterprises, since it hooks in tightly to Microsoft’s software management tools, and there are further improvements to this aspect in IE8. The consumer/business separation is a leaky one so it could still have a big impact.

Technorati tags: , ,

Building Chromium

I’ve successfully downloaded the Chromium source and completed a successful build:

The source is delivered as a Visual Studio 2005 solution, making it relatively straightforward for Windows developers who have this installed. You also need the Windows SDK, but other than that there are few dependencies.

Chromium is not quite the same as Google Chrome. The logo is shades of blue, rather than Chrome’s red green and yellow, and the word Google does not appear at top right in the title bar. If you squint carefully, you can also see that it is a later build: 0.2.151.0 instead of Chrome’s 0.2.149.27 – both at the time of writing.

Oh, and I believe you can download and build without agreeing the onerous Google EULA that is attracting some discussion.

Flash and Silverlight are the Chrome losers, says Zoho boss

Zoho CEO Sridhar Vembu makes an interesting statement in an email he has circulated following the launch of Google Chrome:

The biggest losers in Google’s announcement are not really competing browsers, but competing rich client engines like Flash and Silverlight. As Javascript advances rapidly, it inevitably encroaches on the territory currently held by Flash. Native browser video is likely the last nail in the coffin — and Google needs native browser-based video for its own YouTube; so we can be confident Google Chrome and Firefox will both have native video support, with Javascript-accessible VOM (video object model) APIs for web applications to manipulate video. As for Silverlight, let me just say that if Silverlight is the future of web computing, companies like us might as well find another line of work — and I suspect Google and Yahoo probably see it the same way too.

These last weeks have not been good for Adobe. First there was the Harmony announcement, sidelining the Adobe/Mozilla Tamarin project and making Adobe’s ActionScript 3.0 look more proprietary. Now there is Chrome; and I’m inclined to agree with Vembu, that Google will try to move away from Flash dependency. If that is right, then neither Google, nor Microsoft, nor Apple wants to play the Flash game.

As for Silverlight, I see this more as a Microsoft platform solution, extending its reach beyond the Windows client. I doubt it will be much affected by Chrome, though Vembu is right in saying that the more capable the browser becomes, the less necessity there is for something like Silverlight.

What about Zoho itself? I would take it more seriously if it were not so desperately slow whenever I give it a try, in contrast to Google’s usually responsive servers. It may be better in the USA, or perhaps there is some other reason, but for me the performance just kills it.

Counting primes in Google Chrome

A while back I put together a quick prime counting test for Flash and Silverlight.

As someone noted, this test runs remarkably fast in Chrome, thanks to the V8 JavaScript engine.

Here’s the JavaScript version of the test – note that you cannot easily run this in IE or Firefox for larger values, because the script times out, though you can configure your browser to prevent this.

Here are my figures on Vista (lower is better):

  1. Microsoft Silverlight 2.0 beta 2: 0.464 secs
  2. JavaScript Google Chrome: 1.4 secs
  3. Adobe Flash: 1.667 secs
  4. JavaScript Mozilla Firefox 3: 6.046 secs
  5. JavaScript Microsoft IE7: 11.916 secs

I can’t easily test IE8 as I have it installed in a virtual machine.

Google Chrome: the developer angle

The real purpose of Chrome is to run web applications. Google would like it to be Google applications, of course. Here’s a few things I noticed.

1. The V8 Javascript engine in Chrome is really fast – thanks to just-in-time compilation and other optimizations. This is important, because it removes some of the advantages of plug-ins such as Flash and Silverlight, which also do just-in-time compilation.

2. Chrome includes Gears, which enables offline functionality and other useful services, like a local database engine.

3. This is really part of Gears; but it’s worth noting separately. The Gears Desktop API lets you create application shortcuts – without further permission, apparently. In Chrome this is surfaced as a Create application shortcut dialog:

Note that this is a browser dialog, not a web page dialog.

Why is this a big deal? Well, I recall Adobe’s Kevin Lynch telling me that the usability issue around navigating to an URL in order to run an application was one of the motivations behind the development of AIR, Flash on the desktop. Google reckons it is easier to deal with the usability issue, than to create a separate desktop runtime.

4. Web applications started from shortcuts have no browser furniture. Just the web page in a window. There are probably other ways to get this effect too. I noticed that if you type Ctrl-T while in one of these full-window Chrome pages, which normally starts a new tab, it actually opens a second Chrome window, not just a new tab. Google wants that shortcut to behave like an application, not like a web browser.

Technorati tags: , , ,

Chrome browser memory usage: a good start

If you go to the special url about:memory in Google Chrome, you get a summary of memory usage in all your running browsers, not just Chrome. I tried the following test:

1. Close all browsers.

2. Reopen all browsers – IE7, Chrome, Firefox, Safari – navigate to bbc.co.uk

3. Open the Chrome memory status page:

There are figures for virtual memory as well; I’ve truncated them to make the image fit better. Chrome is easily the smallest.

Microsoft.com blank in Google Chrome browser history

Google Chrome is available for download. I’ve done it in fact; very smooth install. It looks like the company is serious about getting this widely deployed quickly, despite its beta status – there’s a download link on the Google home page – must be important to break the 28 words rule.

Chrome shows your “most visited” sites as a kind of home page. I was amused to see that Microsoft.com shows up here as blank:

No doubt there is a good technical reason. People used to say “DOS Ain’t Done until Lotus won’t run”; and that was not true either.

Update: Honesty compels me to admit that the Microsoft snapshot eventually filled in. Still, it is not much better:

The problem is that the central Silverlight panel is failing to load; the main site looks like this in Chrome as well. OK, so Silverlight doesn’t support Chrome. But Microsoft no doubt has something better than a blank panel for incompatible browsers. Was it warned in advance about the advent of Chrome? Was anyone? I know this is WebKit and that what works in Safari should work here; but we all know that browser compatibility is complex. Still, it is entertaining.

Further update: It looks the same in Safari on Windows! I should explain that there is some more stuff to the right and below the empty panel; but the empty sky background occupies the main part of the page.

To get the full picture, I visited the page with FireFox on Linux:

 

This looks better, but it’s a tease. It has a link to download Silverlight; if you follow it, it eventually reveals that your browser or operating system is unsupported. Sloppy Microsoft; Google exonerated.

More on Chrome soon, no doubt.

Technorati tags: ,