The last two days of using Chrome have had me thinking about the purpose of the Web browser in today’s world. I’ve talked about how Chrome and Firefox have changed how we see browsers, treating them as interactive windows into our daily life, rather than the uncontrolled end of an information firehose.

These applications, that on the surface seem to serve the same purpose, have taken very different paths to this point. Much has been made about Firefox growing out of the ashes of Netscape, while Chrome is the Web re-imagined.

It’s not just that.

Firefox, through the use of extensions and helper applications, has grown to become a Desktop replacement. Back when Windows for Workgroups was the primary end-user OS (and it wasn’t even an OS), Norton Desktop arrived to provide all of the tools that didn’t ship with the OS. It extended and improved on what was there, and made WFW a better place.

Firefox serves that purpose in the browser world. With its massive collections of extensions, it adds the ability to customize and modify the Web workspace. These extensions even allow the incoming content to be modified and reformatted in unique ways to suit the preferences of each individual. These features allowed the person using Firefox to feel in control, empowered.

You look at the Firefox installs of the tech elite, and no two installed versions will be configured in the same way. Firefox extends the browser into an aggregator of Web data and information customization.

But it does it at the Desktop.

Chrome is a simple container. There is (currently) no way to customize the look and feel, extend the capabilities, or modify the incoming or outgoing content. It is a simple shell designed to perform two key functions: search for content and interact with Web applications.

There are, of course, the hidden geeky functions that they have built into the app. But those don’t change what it’s core function is: request, receive, and render Web pages as quickly and efficiently as possible. Unlike Firefox’s approach, which places the app being the center of the Web, Chrome places the Web at the center of the Web.

There is no right or wrong approach. As with all things in this complicated world we are in, it depends. It depends on what you are trying to accomplish and how you want to get there.

The conflict that I see appearing over the next few months is not between IE and Firefox and Safari and Opera and Chrome. It is a conflict over what the people want from an application that they use all the time. Do they want a Web desktop or a Web container?

Tags: add-ons, application, browser, Chrome, extension, Firefox, helper applications, IE, Internet Explorer, web, web application, web applications, Web browser, web container, Web data, web desktop, Web workspace, Windows

Port80 Software is reporting that in their survey of Fortune 1000 Web sites, IIS 6.0 has overtaken Apache as the Web server platform of choice. [here]

My two-cents: I respect the Port80 Software team greatly and love their maniacal devotion to ensuring that IIS users actually make use of the HTTP compression and caching that can so greatly improve Web performance.

That said, they are tied to Microsoft and the IIS platform. I would be curious to see if, scratching below the surface, they were able to determine what the application platform these companies built their mission critical Web applications on. I am open-minded and willing to hear that IIS is winning in that area as well. In my mind, it’s about Web performance tuning, not what you use to get that performance.

That said, I think a critical Web application survey of these same firms would find that many of these companies rely on JSP servers to run their core business processes.

As well, it would be interesting to se, by Fortune 1000 ranking, what the companies are using what server platform.

And…people still use Netscape Enterprise, SunOne, and Domino as production Web servers? YIKES!

Tags: apache, app, application, business, business process, caching, compress, compression, critical, cro, HTTP, IE, IM, it, js, LAN, Microsoft, Om, One, performance, pr, run, server, users, web, web app, web application, web applications, Web Performance, Web server, Web servers

Yes, I know. For the fourth time in a week, this is a post with a link to my resume.

But last night, while I was writing an e-mail to someone about the long-term future of GrabPERF, I wrote something that I had to read twice when it came out.

GrabPERF is my resume.

How can a simple Web application be a resume?

In my case, it highlights all of the things that I am interested in:

• Web performance
• Statistical analysis
• Clear presentation of data and information
• Web development skills
• Database administration skills
• System administration skills
• Distributed systems

GrabPERF showcases everything that I have taught myself over the last seven years. And I am proud of it.

So, what do you use for your resume?

Technorati Tags: GrabPERF, resume

Tags: analysis, app, application, data, database, EAD, GrabPERF, GrabPERF.org, HTML, HTTP, IE, IM, information, it, Om, One, performance, pr, Technorati, web, web app, web application, Web Performance

This week, I had a conversation that included a discussion of whether Microsoft Office applications should be webified.

I think that this is the only way that MSFT is going to be able to get people to support a new version of their product. A web application running on an IIS server (you think they would make able to run on Apache? PSSSHAW!) would support thousands of users, even remotely (HTTPS).

How? Well, once you load the Web app…the load is effectively off the server until the user needs to save, or import, or merge, or speel…spellcheck. Users get to free up cruft and crap from their machines by only loading apps when they need them, and only the apps they need.

OWA is already good enough to replace the bloatware we call Outlook.

As one lunch companion pointed out, there has to be a version of these apps running in a lab somewhere in Redmond right now.

I would buy access to a new version of Office served over the Web in a heartbeat in order to dump the cruft and creep that currently occupies 300MB of drive space.

Tags: apache, app, application, conversation, cro, current, EAD, HTTP, IE, IM, it, Mac, Microsoft, Om, One, Outlook, pr, run, server, users, web, web app, web application

As the Web moves toward the delivery of services, I have been ruminating on the continuing importance of browsers.

Scoble writes:

Oh, well, back to my RSS news aggregator. That’s where I spend 90% of my Internet time now anyway. Are you still using a Web browser? Good. I’ve been telling audiences that those of you still using Web browsers are wasting your time. I think that Opera might be more concerned by that.

I agree. I use Firefox to handle large applications, such as my employers interface, and my blog editor, but beyond that, it has become less and less important in my everyday online life.

This is the trend. HTTP and HTTPS will be the vehicles to deliver this data. Web servers will become more and more important, but as transformation and application servers for back-end data, not as presentation and image servers.

This is a long-term trend. But it also explains things like the decline of Slashdot. Although they have had an RSS feed for a long time, their bleeding-edge readers found that Slashdot was no longer bleeding-edge. Information is flowing faster and in a more personalized manner through aggregator, desktop and online.

I agree with Scoble (something that happens infrequently): the browser war may be irrelevant. The Web Application era has begun.

Tags: app, application, audience, blog, browser, browser war, data, delivery, desktop, EAD, Firefox, HTML, HTTP, IE, IM, information, Internet, it, live, Om, online, personal, pr, RSS, server, web, web app, web application, Web browser, web browsers, Web server, Web servers

I submitted a presentation proposal for OSCON 2005 just now. The abstract is below.

The Open Source community has driven the online world for the last decade. PHP, PERL, Apache, Java, and MySQL are all major components of large online enterprises.

However, putting an application online and ensuring that it satisfies the performance, availability and reliability demands of the increasingly knowledgeable online consumer are often two separate concerns.

Performance should not be an afterthought; performance should be a leading force in creating a Web application.

Using simple Open Source Tools, Web performance measurement solutions can be built that rival commercial solutions. But what does this data tell you? And how do you turn this into useful business information?

This discussion will expose the participants to key Web performance metrics that make sense to both technology and business leaders in your organization.

I have a snowball’s chance in hell of having it accepted, as it is not hip, technical or trendy, and I am not an Open Source Guru, but if you design stuff for the Web, then you better be ready to have your site examined in detail, because if you don’t do it, your customers will.

Tags: apache, app, application, business, community, components, customers, data, design, EAD, HTTP, IE, IM, information, IP, it, measurement, metrics, mysql, Om, One, online, online world, OReilly, performance, performance measurement, Perl, PHP, pr, Reliability, web, web app, web application, Web Performance, Web performance measurement