Take browsers to the limit: Google

Take browsers to the limit: Google

Summary: The only way to transform the Web into the desktop platform of the future is to fully embrace bleeding edge features in browser software. This advice came from the lead engineer of the Google Maps project, Lars Rasmussen.

TOPICS: Google, Browser
The only way to transform the Web into the desktop platform of the future is to fully embrace bleeding edge features in browser software.

This advice came from the lead engineer of the Google Maps project, Lars Rasmussen.

Speaking at a conference on Web engineering in Sydney, Rasmussen said Maps' use of the XSL+ (Extensible Stylesheet Language) standard and Microsoft's Vector Markup Language as examples of useful technologies seldom used by Web developers. Both are only supported by certain browsers.

If a Web application takes advantage of the best technologies a user's browser can offer, then "each individual gets the 'sexiest' experience in their browser", he said.

"Go beyond browsers' lowest common denominator," he advised developers.

For example, Maps can command Internet Explorer to use VML to display a blue line between geographical points, but use a PNG graphic format and a linear description for the Firefox browser.

The Sydney-based developer revealed the release of Maps created a critical mass of interest from the programming community in the development of AJAX (Asynchronous JavaScript and XML) applications, or Web applications with sophisticated graphics.

Rasmussen said when browser makers saw companies with huge user bases like Google actually using next-generation technology like VML, they became much more enthusiastic about including such innovations in their browsers. An example of this was the upcoming Scalable Vector Graphics support in Firefox, he added.

"Google Maps was originally a C++ app intended to be downloaded separately," he recalled, going back to the days before his startup company, Where 2 Technologies, was acquired by Google last October.

However, that changed when Rasmussen and his colleagues -- looking for some venture capital -- pitched their mapping expertise to Google.

At that point, the team changed their development model and started focusing on the Web instead. "We were surprised by the things you could do in a Web browser," he said.

Firstly, the Web allows rapid deployment and there is no software for users to install. It's also much easier to make sure code runs on multiple browsers compared with multiple operating systems like Mac OS X and Windows.

The downside is that browsers don't give programmers full access to a computer's resources such as memory, process power and hard disk space. This is a bottleneck the engineer sees being removed in future, although he thinks the simplicity of the current Web browsing experience needs to be maintained.

As such, Rasmussen remains disappointed with Google Earth, which is similar to Maps but utilises three-dimensional modelling and has to be downloaded prior to use. "Much as we have tried, we haven't been able to do this in JavaScript," he said, expressing hope that Google Earth and Maps would eventually be merged into one Web application.

Google hiring
According to Rasmussen, Google is looking for Web mapping experts to beef up its Sydney office.

Topics: Google, Browser

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • AJAX is NOT "web applications with sophisticated graphics"! This is the second time I have seen a CNet article completely miss the point on what exactly the term "AJAX" refers to. Nowhere in "Asynchronous JavaScript and XML" is "graphics" mentioned!

    AJAX refers to the ability of a web app to talk with the server and respond dynamically to user interaction without redrawing the screen. It could do this just as easily with a text-only application as with a graphics-intensive app such as Google Maps.

    Please, CNet, get this straight! If you're going to latch on to the latest buzzwords, at least use them correctly!
  • Here is a quick comparison of Google Maps and Virtual Earth:
    Just wanted to add my $.02 on taking the browsers to the limit. It should be dependant on the application. A financial company's website, for instance, is more interested in posting its information to as many users (read 'browsers') as possible and is better off using the least common denominator. There is, of course, a reasonable limit here. There is the LCD that you code for with full functionality. Any browser below that limit gets some functionality and a message stating that they might want to upgrade to get all features.
    And our anonymous poster is correct in pointed out that AJAX is NOT "web applications with sophisticated graphics"!