HTML 5, Google I/O and Evolution of Applications.

Earlier this week, I had occasion to attend the Google I/O conference. This blog post is more reflective than a factual report on the event. (For factual reports, e.g., see Google: The browser is the computer, Google Wave: A new kind of mega-application).

In the beginning, e.g., with the ENIAC, people programmed in 1s and 0s. The initial tedium was avoided by the invention of assembly language programming. The primitives that the programmers dealt with included registers, memory and i/o in the form of tapes and disks.

Subsequently, there were several high level programming languages invented, stack machines supported block structured languages. For a very long time, the stack machine seemed sufficient, and even the concept of classes were implemented on top of the stack machines. The primary commercial successes in this arena are C/C++ and Java and their variants.

In this conference, the primary message appears to be that the communication content, in Google Wave, is modeled as hosted XML documents, and the primitives that a programmer uses within a browser are the ones that manipulate the document object model (DOM); and, there are several new primitives, i.e., tags like canvas, video, audio, etc., built natively into HTML 5. (A good introduction to the model methods is available at HTML DOM Primitives and XML DOM Primitives). Thus, while the stack machine continues its reign, additional functionality is being expected of the platform in terms of the DOMs.

To promote concurrency in applications, the concept of Web Workers is available in HTML 5.

What happened in the last 50 or so years? Now, the basic computational platform (within a browser) is one that supports very granular manipulation of pieces of communication that is relevant among human beings (and computers), rather than registers, stack, etc. This is good; it is easy to see progress.

Now, in the future, why would anyone want to build non-browser applications? Particularly since JavaScript engines seem to be gathering better performance all the time? Chrome's V8 JavaScript engine is available as open source. (There is a separate web page (v4) to assess V8's performance of a browser on your computer).

The state of globally accessible health information on the Internet.

The Google blog post titled Listening to Google Health users is illustrative of the work in front of us before we can claim universal accessibility of health information over the net. The ICD codes have been in use for quite some time now, since 1893 in some form or the other, but the Google Health episode brings forth the need for greater accuracy in defining these codes and their descriptions.

The point to be noted is that computerization greatly helps, and sometimes accelerates, correct classifications.