Webware

Google, ever eager to renovate the computing industry for the benefit of the Web and its own business, is working to link two nascent but potentially significant projects, its experimental Go programming language and its Chrome Web browser.

Gordon, Go's gopher mascot

Specifically, the company is building a foundation to let programs written in Go run directly within a Web browser endowed with Google's Native Client software. Native Client is designed to let browser-based programs run faster than is possible with today's widely used JavaScript; though it's still in its early stages, it's built into Chrome and available as a plug-in for other browsers.

A little poking around the Go source code reveals a reference to NaCl, the abbreviated name for Native Client. And Native Client is indeed on the Go agenda, said Rob Pike, one of the five core members of the Go team, in a Wednesday interview.

"We have an embryonic implementation of the NaCl support for Go using 8g," a compiler that produces code for x86 chips such as Intel's Core line, Pike said. "It's restricted by a couple of details of NaCl's implementation, but we hope to see changes to NaCl one day that will make Go a full-fledged language in that environment."

The Native Client compiler--the tool that converts what people write into software a computer can run--is specially modified to screen out a variety of software instructions that could expose a computer to an attack from a Native Client module downloaded off the Web. And the Native Client software itself checks such modules before they run. The result, if the security approach stands up to security scrutiny, is browser-based software that runs close to the speed of ordinary software that runs natively on a PC.

Rob Pike discusses the Go programming language at a Google Talk

(Credit: Google)

Native Client has been maturing, the most recent stage being inclusion of NaCl within Google's Chrome browser, though disabled by default for now. Google is using Chrome as a vehicle to distribute other Web technology, too, including Gears, which can let people use Gmail while offline, and WebGL, which gives hardware acceleration to 3D graphics in the browser.

Go is only experimental at this stage, but Google hopes to use it to produce some of the software running on its vast array of servers. Google's scale makes even academic projects potentially commercially relevant, which is enviable to many companies who've tried to get projects off the ground.

Indeed, an episode earlier in the Go team's history is illustrative. Pike, Unix co-inventor Ken Thompson, and Russ Cox all worked on the Plan 9 operating system project that, like Unix, began at Bell Labs. (Yes, Plan 9 is named after Ed Wood's famously bad movie, "Plan 9 from Outer Space.")

Unlike Unix, Plan 9 didn't have much commercial success, although Vita Nuova does sell a version called Inferno. Getting a mainstream operating system off the ground is hard: you must convince programmers, software companies, and hardware makers to embrace it; you must convince people to use it in the real world; and you must keep pace with the evolution of entrenched operating systems.

A bit of Plan 9 lives on inside the Go project, with various Plan 9 tidbits appearing in the Go source code. Pike, though, says there's not much.

Glenda, the Plan 9 bunny mascot, looks similar to Gordon, Go's gopher mascot. Both were drawn by Rob Pike's wife, illustrator Renee French.

(Credit: Bell Labs)

"The 6g/8g/5g compilers are almost completely new but are tied to the open-source Plan 9 compiler suite's C compilers and linker," Pike said. "That's really about it except for the obvious historical connection for some of the protagonists: Ken, Russ, and myself."

Programming languages face similar challenges as operating systems in getting off the ground: A lot of interdependent elements in the ecosystem must all be built simultaneously. It's what's known in the trade as the chicken-and-egg problem: you can't make a chicken without an egg or vice versa.

But Google makes things different for Go. It's devoting real resources to the project and believes it could be useful on its own servers to run software such as the Gmail service Web browsers tap into. It's got the chicken and the egg under its own roof.

And with the money Google could save by increasing the performance or efficiency of its servers even just a fraction of a percent, it has abundant financial incentive to make things work.

Marrying Go to browsers is just another aspect of the same issue.

Assuming Go and Native Client mature enough to be useful, Google can't mandate that Web developers embrace them; indeed, they generally haven't embraced Gears even though it can help with some Web site matters. But again, Google has a browser and some awfully big Web sites it can use to get the ball rolling.

Mozilla, racing to release Firefox 3.6 before the end of the year, has released a second beta of the open-source browser for Windows, Mac, and Linux.

Firefox 3.6 beta 1 introduced most of the new features, most visibly the ability to customize Firefox's look through Personas, less than two weeks ago. But among the 190 patches in the new beta is what Mike Beltzner, Mozilla's director of Firefox, described in a blog post as "a mechanism to prevent incompatible software from crashing Firefox."

There also are a number of deeper changes in Firefox 3.6 that Web developers likely will be more interested in. Note that one of them, the ability to use color gradients with formatting technology called Cascading Style Sheets (CSS), has changed syntax in between Firefox 3.6 beta 1 and beta 2.

Mozilla is trying to accelerate the pace of Firefox releases; Firefox 3.7 is set for release in the first half of 2010 and 4.0 some time later that year. The project faces new competition from Google's Chrome browser.

Five years ago, Mozilla made it clear that the browser wars weren't over after all.

Images: Firefox through the ages

View the full gallery

In the 1990s, Netscape had lost its dominance in the browser market to Microsoft's Internet Explorer, and the Netscape-spawned open-source project called Mozilla had sunk into obscurity. Even a federal antitrust suit accusing Microsoft of anticompetitive practices with its browser and Windows was not enough to turn the tide.

But on November 9, 2004, Firefox 1.0 emerged to fight back again.

The project, originally named Phoenix to symbolize rebirth from Netscape's ashes, has now clawed its way back to account for nearly a quarter of the browser usage today. Microsoft may not be on the run, but it's on the defensive, gradually building its browser development effort back up into fighting form.

More people will get a chance to try out bookmark synchronization with Monday's release of a beta version of Google Chrome for Windows.

Google introduced the bookmark sync feature for the developer-preview version in August, but now it's also in the better-tested beta version, Chrome 4.0.223.16. However, there's still no Chrome beta for Mac OS X or Linux.

In a video explanation, Google's Anthony LaForge somewhat breathlessly describes how the sync feature can keep bookmarks the same on multiple machines. That's a fair point, but let's be realistic here--bookmark sync in Chrome is more catch-up than paradigm shift. Indeed, with the popular Xmarks extension--in the works for Chrome, people can synchronize bookmarks among multiple browsers, not merely multiple computers.

And Chrome's clever message-based sync technology notwithstanding, Chrome bookmarks would be a lot more magical if they synchronized with the Google bookmarks service, which is linked with iGoogle and the Google Toolbar.

Speaking of extensions, one of the 4.x series' biggest features is the ability to accommodate extensions, but because Google is shifting the extensions interface, the feature isn't enabled in the beta version. Chrome is released in three versions: the roughest, fastest moving developer preview, the more stable beta, and the stable edition for the broadest audience.

The 4.x series has other significant features, too, though it's not clear whether they'll arrive in the beta or stable versions. One is Google's Native Client, which lets JavaScript applications take more direct advantage of a PC processor's horsepower through a careful security mechanism. Another is WebGL, a 3D interface that does the same with hardware-accelerated graphics.

Together, the features have the potential to dramatically improve the power and sophistication of Web-based applications. That's particularly interesting given that Google is building Chrome OS, a browser-based operating system.

The Mac version isn't in beta yet, but it's a priority.

"Our goal for this Friday is to be able to count our Mac P1 M4 release blocker bugs on one hand (we're in the 20s now)," said Chrome programmer Mike Pinkerton in a mailing list announcement on Monday. P1 bugs are priority-one; M4 refers to milestone 4, or version 4.0.

And Google is willing to put more manpower onto the Mac version, he added. "Everyone should have their P1 list practically at zero by the end of this week. If you are not going to be able to reach this, let me (or other triage folk) know ASAP so that we can get you some help.

Chrome edged up to 3.6 percent of browser usage for October, its highest showing so far in Net Applications' statistics since the browser's first public release 14 months ago. That's within striking distance of third-place Safari at 4.2 percent, but still well short of second-place Firefox at 24.1 percent and dominant Internet Explorer at 64.6 percent.

Chrome has helped fan the browser war flames even without becoming dominant, though. In particular, it's helped increase the emphasis on performance such as the speed to load the software, load Web pages, and run Web-based JavaScript applications. Here, more than with bookmark sync, Google's chest-thumping has some merit:

"As with every release, this new beta comes with many speed improvements. In particular, as Web applications we use every day become increasingly dynamic, browsers like Google Chrome need to be able to construct and change elements on web pages as fast as possible," said programmers Idan Avraham and Anton Muhin in a blog post. "We've improved performance scores on Google Chrome by 30 percent since our current stable release, as measured by Mozilla's Dromeao DOM Core Tests, and by 400 percent since our first stable release."

There has been some slowdown with the arrival of Chrome extensions, though, so Google will have some more optimization work to do to keep the browser in fighting trim.

Updated 9:57 p.m. PST with further details on the Mac OS X beta priority.

Betting that the benefits of the move will outweigh the risks, Yahoo has released the source code underlying in-house software called Traffic Server that can speed up Web site operations.

The software works by moving some data and operations closer on the Internet to the people trying using those services. Yahoo released it as an "incubator" project under the auspices of the Apache Software Foundation, a seasoned organization for managing open-source projects and also the site that houses the Hadoop open-source project Yahoo favors for large-scale data-processing challenges.

Shelton Shugar, Yahoo's senior vice president of cloud computing, plans to announce the move at the Cloud Computing Expo in Santa Clara, Calif., on Tuesday in a keynote speech, but the software actually arrived at Apache last week.

Shelton Shugar, Yahoo's senior vice president of cloud computing

(Credit: Screenshot by Stephen Shankland/CNET)

"We've donated Traffic Server to Apache because we think it's a great piece of code, and we want to build a community around that in the same manner we built a community out of Hadoop," Shugar said in an interview.

Traffic Server is a battle-hardened package with more than 200,000 lines of C++ code. Yahoo originally got the software through its acquisition of Inktomi earlier this decade, and it's been using it ever since. Today, the software delivers 30 billion Web objects and 400 terabytes of data each day.

And Yahoo can rightly be proud of Traffic Server's performance: that comes from a surprisingly small number of Yahoo servers--between 100 and 150, said Chuck Neerdaels, vice president of data services at Yahoo. The software is set up particularly to run multiple tasks at the same time, a design well-suited to today's servers with multicore, multithreaded processors.

Source code is what humans write in a higher-level programming language; only after it's been translated into binary machine code can a computer actually run that program. When associated with an open-source project, this software is available for anyone to see, modify, and distribute, in contrast to the locked-down world of proprietary software such as Microsoft Windows. So in effect, Yahoo is allowing others not only to use Traffic Server for their own ends, but also to modify it--for example, by taking advantage of its ability at to accept plug-ins that can adapt it for different tasks.

Giving away the farm?
So isn't there a risk that Yahoo is giving away some pretty important technology that's central to its business? Plenty of start-ups today are trying to grow to Yahoo's scale, and many of them are competitors.

Some Yahoo rival might very well gain as a result, but on balance, the company thinks that it'll come out ahead. For one thing, Traffic Server in isolation is not as powerful as Traffic Server woven into Yahoo's computing fabric, the company argues.

"What we're giving up is a generic building block. What makes it really interesting at Yahoo is how we've connected it with other things to make a bigger service," Neerdaels said. As for Yahoo's major rivals: "We suspect our larger competitors already have some solution they're happy with."

Yahoo expects a number of benefits from broader development and use of Traffic Server.

"We think a lot of folks can benefit from this, and by raising the tide, we think we can benefit as well," Shugar said.

For one thing, making Traffic Server open-source software will mean that people will grow familiar in its use, making it easier for Yahoo to hire engineers who already are up to speed.

"By virtue of basing services on open-source software, we attract people who want to work on open source. They like it, and they like the idea of it. It's a skill they can take with them from one place to another," Shugar added.

For another, Yahoo can benefit from others adapting the software to a broader range of uses, he said.

Gaining influence among developers
There are intangible benefits, as well, when it comes to recognition among programmers, whose influence in some ways makes them the digital elite. Microsoft long ago learned that much of its power comes from developer allies, and Google is trying to put that lesson to good use as well by releasing many open-source projects--Google Chrome being one recent example.

Yahoo isn't in the business of selling technology to others in the manner of Amazon Web Services, Microsoft Azure, or Google App Engine. But having solid technology is essential to Yahoo. While it's willing to sell its search business and engineering skills to Microsoft, it still needs in-house expertise to power its many Web properties and to reduce its operating costs.

Here, Traffic Server is important. For example, one area where Yahoo uses Traffic Server was at Yahoo Sports for handling scores. A regular Web server sends out the Web page to a person's browser, but Traffic Server handles the JavaScript technology that periodically refreshes the contents of a scoreboard element on that page.

It's only a "trickle" of data, but at Yahoo's scale, that can be some pretty heavy work. "When they moved to using the Traffic Server front end, they shaved something like 200 machines off their back end because session management was more efficient," Neerdaels said.

Another part of Yahoo operations retrofitted with the software is Yahoo Mail, he said. Traffic Server can be used to process the cookie text files on a person's browser to figure out whether that person can be logged in automatically or the person needs to authenticate anew. It also can route traffic appropriately when, for example, a person who is "homed" to Yahoo's servers in India visits the site while in the United States.

Traffic Server also manages a lot of more nuts-and-bolts tasks. For example, it can cache Web data closer to browsers so the original Web servers that house the data aren't as overtaxed. And it can store a Web address stored in the Domain Name System to speed up network speeds.

What's it good for?
Some of these chores can be handled by existing software, such as Squid, which is already open source. But Yahoo is on a roll with its open-source work, as the company seeks to advance its internal cloud-computing infrastructure. Expect more to come.

"As various pieces of our cloud get to a point of maturity, we will open-source specific pieces," Shugar said. Future candidates include Yahoo's foundation for hosting its Web applications on a virtualized, more flexible foundation, and its Sherpa and Mobstor services for storing data.

Winning open-source allies can be difficult, and Neerdaels said it takes an engineer a good six months to fully comprehend all Traffic Server's code, so immediate gains beyond fostering goodwill are unlikely.

But in the long run, Yahoo's program could pay significant dividends. Building a series of significant open-source packages could lead to a Yahoo infrastructure that's high-power but more standard than custom-made.

It's not every day that large, significant software packages arrive on the Net in open-source form--much less a series of them that are increasingly relevant to a competitive market of large-scale Web sites.

In this case, Yahoo's gift may indeed become Yahoo's gain.

With all the hubbub about Snow Leopard and Windows 7, there's another operating system out there you may not have noticed that's getting a significant update: Ubuntu Linux.

Ubuntu backer Canonical plans to release its "Karmic Koala" version on Thursday, and both the desktop and server versions of the open-source operating system take significant steps toward cloud computing. The concept of moving work away from the computer in front of you and into the network does have some merit, but cloud computing is today's fashionable buzzword, and Canonical Chief Executive Mark Shuttleworth is sensitive to its overuse.

Canonical CEO Mark Shuttleworth speaking at the Intel Developer Forum

(Credit: Stephen Shankland/CNET)

"What frustrates me is the term 'cloud' has come to mean anything with an Internet connection, including some stuff that really looks familiar like internal IT," said Shuttleworth in an interview. It's fair to say that in Ubuntu's case, though, it's not a stretch.

Built into the server version of Ubuntu 9.10 is Ubuntu Enterprise Cloud, technology built atop the Eucalyptus software package. Amazon Web Services (AWS), a collection of computing infrastructure accessible over the Net on a pay-as-you-go basis, is among today's most significant cloud-computing efforts, and Eucalyptus implements many of its functions so companies can build their own "private clouds" using the same services.

And in the desktop version of Ubuntu, the cloud connection is a service called Ubuntu One, which lets Ubuntu users synchronize files stored on different machines and back them up on the central service. Storage space of 2GB is free, and 50GB costs $10 per month.

The Ubuntu software itself is free; Canonical sells Ubuntu support services.

MOUNTAIN VIEW, Calif.--John Lilly wants it both ways.

Working at Mozilla Corporation since 2005 and as chief executive since early 2008, he helped oversee a remarkable achievement. Mozilla has built the Firefox browser from a largely unsuccessful remnant of the Netscape era of the 1990s into the browser that nearly a quarter of people on the Web use. Now the challenges are different.

Mozilla Corp. CEO John Lilly

(Credit: Stephen Shankland/CNET)

First, for new growth, Mozilla must make its open-source browser appeal to an even more mainstream crowd, one that's more interested in working and playing online than in sticking it to Microsoft or being part of a cause. Second, it's got to keep the loyalty of the technically savvy early adopters and Web developers that Google now has been courting with its Chrome browser.

"We have to do both," Lilly said in an interview at Mozilla headquarters here. "We have to be a better browser for your standard everyday user of the Web who uses IE now, but I think we have to redouble our efforts to be good for Web developers."

The world changed for Mozilla when Chrome burst onto the scene in 2008. Mozilla didn't see itself as complacent, but Chrome was a wake-up call that "clarified some of our priorities," Lilly said, including snappy performance.

"It made some things real crisp," Lilly said.

Indeed, in the months after Chrome's arrival, these priorities appeared in Mozilla's Firefox planning: "Observable improvements in user-perceptible performance metrics such as start-up, time to open a new tab, and responsiveness when interacting with the user interface. Common user tasks should feel faster and more responsive." And future versions of Firefox likely will look more like Chrome embracing some of its less obtrusive framing of Web content and applications.

'Web-native' Google
Mozilla's biggest rivals before, Microsoft's Internet Explorer and Apple's Safari, came from companies firmly rooted in the era of desktop computers and operating systems. Not so Google, which not only has Web-based applications such as Google Docs and Gmail to support, but also a browser-based operating system called Chrome OS.

"Competing was hard but at some level simple. Google is much more Web-native," Lilly said.

Google is an unusual rival. Even as Google and Mozilla vie for popularity, they're tight allies in the "Open Web" movement to augment Web standards to today's static pages into tomorrow's applications. And Google almost singlehandedly funds Mozilla by sending back a portion of search-ad revenue that originates from Google searches within Firefox.

In 2007, the last year for which Mozilla has released figures, Google supplied 89 percent of Mozilla's $75 million in revenue. Although the Mozilla-Google revenue-sharing deal is set to expire in 2011, realistically, it's probably safe.

For one thing, Firefox sends a large amount of search traffic to Google--traffic it could easily send to another search engine with the flip of a default setting switch. Second, Google's browser enemy is Internet Explorer, especially the slow and limited IE 6 that's still in widespread use eight years after its release. If Google wanted to cripple Mozilla, the time to do it would have been 2008, when the search-ad deal was up for renewal, but Google renewed it.

New standards
One big part of Mozilla's effort to remain in the vanguard is support for new Web standards.

Mozilla is among those trying to renovate Hypertext Markup Language (HTML) to make it a richer, more capable foundation for programming as well as display. And its significant if not dominant share of usage makes it a major force bringing those "Open Web" technologies to fruition.

"There are still a lot people who think the Web is done--there's this big mission accomplished banner. It's not true," Lilly said. "There are many proprietary technologies, many walled gardens with respect to video and offline technology. There is still is a lot of the Open Web fight to fight," Lilly said. "Getting to Firefox--a quarter of the Web--shows these technologies are real."

One thorny one is Web-based video. Today most online video is sent using Adobe Systems' Flash browser plug-in, which is free; video is encoded with the H.264 standard, which must be licensed. But fees could increase in 2011 with the possibility of new royalties for streaming H.264 video over the Internet.

Mozilla headquarters in Mountain View, Calif.

(Credit: Stephen Shankland/CNET)

Perhaps not coincidentally, Google announced plans to acquire On2 Technologies, which has other video encoding and decoding software--or codec--including a new version under development called VP8.

"If VP8 is an open codec and unencumbered (by patent licensing considerations), it's something we'd implement. That changes the whole landscape," Lilly said.

The first update in a decade to the HTML standard used to describe Web pages is under way, and one major feature is a video tag that builds video directly into the Web rather than relying on a plug-in such as Flash, Microsoft's Silverlight, or Apple's QuickTime. Though Mozilla, Google, Apple, and Opera all like the tag, they don't see eye to eye about what format video should be encoded in, which complicates how well the technology works in practice.

Mozilla and Opera urge use of the Ogg Theora video format, which may be implemented in open-source software without licensing complications, and Firefox has had Ogg support since version 3.5 of the browser arrived earlier this year.

But Apple's Safari has H.264 support built in. Google's Chrome supports both standards, but YouTube supports only H.264. Microsoft hasn't said what it plans to do. So for now, video plug-ins appear unthreatened.

Microsoft in the wings
At the other end of the competitive spectrum is the incumbent. Although Microsoft's browser development crept nearly to a standstill after IE won the first browser wars of the 1990s, there's evidence the sleeping giant is awakening.

IE 8, released earlier this year, attempts to conform to existing Web standards rather than setting its own. And though IE still doesn't support many of the latest technologies to make the Web into an application foundation, Microsoft now is actively engaged in discussions over those technologies and their standardization. Finally, Microsoft is working on Web applications of its own in the form of an online version of Office 2010, giving the company a strong new incentive to improve its technology.

So far, though, Microsoft's effect is more theoretical than actual.

"They've given notice they will engage. We haven't seen them influence it a lot," said Mike Shaver, Mozilla's vice president of engineering. He's eager about the possibility that Microsoft will embrace new Web standards. "They represent a large user base--some by choice, some not. Those technologies mean a lot more when they make it to more people."

Something of a wild card factor in today's browser wars is Apple, which has released a Windows version of its browser. The company rarely ventures out of its home turf of Mac OS X unless there's a strong incentive--releasing iTunes for Windows to boost the iPod business, for example--but evidently deemed Safari for Windows a high enough priority to fund development and support efforts if not much in the way of marketing.

Going mobile
Apple, though, has a big head start when it comes to the new era of mobile browsing that's just beginning to mature with high-powered devices such as the iPhone. Like it, Palm's Pre handset and Google's Android operating system for mobile phones use a browser based on the open-source WebKit project.

Firefox is moving more slowly into mobile, though. Its mobile browser project, called Fennec, is slated to emerge later this year under the Firefox brand name for Nokia's Maemo mobile operating system, and Lilly has said Firefox will be available for Google's Android operating system as well.

"I do more browsing than ever in mobile. The boundaries between desktop and mobile are going to blur," Lilly said. "We will release (Fennec) as a product called Firefox later this year."

Lilly likes to look at the bright side of this fluid landscape. "In most ways the world as a Web user is better than it's ever been. There's real choice, not just from Apple and Microsoft but from Google and Opera," he said.

"We're a unique organization. Compared to open-source projects, we look rather wealthy. Compared to the people we're competing with--Apple, Microsoft, Google--$50 million, $60 million, $100 million in revenue that to them isn't really meaningful," Lilly said. "We're competing in a low-expense, scrappy way."

Mozilla has released the first alpha version of Firefox 3.6 for Windows, Mac, and Linux, a browser with speed improvements and new features the organization hopes to finalize faster than its predecessor.

"Unlike the year that passed between Firefox 3 and Firefox 3.5, we expect that this 3.6 release will be released in a small number of months," Mozilla evangelist Chris Blizzard said in a blog post Friday.

Firefox 3.6, code-named Namoroka, has a variety of changes, but it's not as dramatic a departure as 3.5 was from 3.0. Among the 3.6 features are faster JavaScript, the Web programming language Firefox executes with its TraceMonkey engine; faster page-rendering speed; some new features for CSS (Cascading Style Sheets) technology for controlling some of the look of a Web site; and a feature called the compositor that handles complicated layout circumstances better.

Performance is a big issue with browsers these days as people spend more time using them and programmers create more sophisticated sites and applications that live on the Web. All major browser makers are emphasizing performance improvements in their newest versions.

Download links for the first Firefox 3.6 alpha are at the Mozilla Developer Center.

Google's move to let software run natively on Android devices opens the door for a version of Firefox that can run on the operating system.

At present, Android applications are written in Java and run on Google's Dalvik Java virtual machine. Last week, though, Google announced the Android Native Development Kit version 1.0 that lets software run natively on the Linux layer below, though the company sees it as a way not to run full-fledged applications as much as to run components of ordinary Android applications.

"Android applications run in the Dalvik virtual machine. The NDK allows developers to implement parts of these applications using native-code languages such as C and C++," said Google's David Turner in a Native Developer Kit blog post.

That's enough to whet the appetite of Mozilla, the organization that oversees development of Firefox and its mobile incarnation, called Fennec though likely to sport the Firefox name when it arrives in product form.

"Developers are taking a look at the NDK to see if it provides the capabilities we need to bring Fennec to Android. If it's possible, I think our community would be interested in doing it, because Android will be appearing on more smartphones with the capabilities to provide a good browsing experience," said Jay Sullivan, Mozilla's vice president of mobile.

A year ago, Mike Schroepfer, then Mozilla's vice president of engineering before he moved to Facebook, said Mozilla wasn't focusing on Android because of the Java constraint and because Android already has a capable browser of its own.

"We've been concentrating on other platforms that don't have browser or didn't have a good one," Schroepfer said in May 2008. "I'm looking forward to (Google) opening up the entire platform. Today I can't get Firefox on Android because I don't have the API (application programming interface) support.

The browser that ships with Android is based on the open-source WebKit project. That's the same foundation for Google Chrome, Safari on Mac OS X and the iPhone, and the browser on the new Palm Pre, making it something of an incumbent power among high-end mobile phones.

It's not a simple choice to releasing software that uses the Native Development Kit. Using the higher-level Java foundation insulates programmers from worrying about what underlying hardware is in a phone or other device, but using native code means the software must be tailored for a specific processor. It also means that software won't have access to many system-level features that are part of Android.

And writing native code can help boost performance, always a problem on mobile phones with limited hardware and battery life. In a parallel situation on PCs, Google has released software called Native Client that lets browsers run software natively processors for better performance.

Mozilla is interested in a variety of sub-PC devices. "We're also very interested in Netbooks across the operating system and chip architecture spectrum," Sullivan added. "Firefox, Fennec, and other Mozilla-based browsers have been demonstrated on Netbooks running Windows CE, various Linux variants, and Moblin," a Linux-based operating system for mobile devices backed by Intel.

Firefox's core use is on personal computers, though. There, a new version is imminent.

"The Mozilla team is mobilizing to ship Firefox 3.5, and it's looking like Tuesday morning" will be the ship time, Mozilla said in a statement Friday.

However, Mozilla also has issued three candidates instead of the expected one, and in the bigger picture added many new features to 3.5 that kept its release back months compared to the earlier, smaller-scale Firefox 3.1 plan, so give the organization some wiggle room.