Sign in
in
   
"It is the mark of an educated mind to be able to entertain a thought without accepting it."  -Aristotle

About Me

I am a co-founder of Notches, an early stage startup currently based in NYC. We are building a free, open reviews network that anyone can participate in and anyone can build on top of. You can find out more on our official blog.

Read more about my background.

Connect with me on...

Recent Readers

Flickr Photos

 

Warning:

This article is more than 45 days old. Given the speed at which the technology world moves, this post is probably somewhat out of date. Please keep this in mind when reading the post. If this is a tutorial, please check whether you are using the same versions mentioned in the article.

The problem with - and promise of - Web 2.0, AJAX and other awful buzzwords

I've been a champion of the ideas behind "Web 2.0" for a long time, but I absolutely deplore the term - and probably as a result haven't talked about it as much here I would have. 

It's a general problem I have with most of these kinds of buzzwords used to decribed paradigm-shifting technologies: they're vague, overbroad, ill-defined, and most of all trivialize what is really going on in the first place.

Michael Swaine makes this point in the most recent edition of his always -excellent Swaine's Flames column.

Onions to "Web 2.0." Uhh, does Tim Berners-Lee get a say in when the Web gets revved? Or is it the rule that anybody named Tim gets to start his own Web? Internet2, IPv6, those terms actually refer to something. But Web 2.0: What's that exactly? Nobody seems to know. Last September Tim O'Reilly,
 who, along with his coconspirators at O'Reilly & Associates, coined the term, tried to explain what Web 2.0 was and/or wasn't. That essay convincingly demonstrated that Tim doesn't know either.

He did, however, attempt to define it himself.

If Tim (either of them) can't define it, I certainly shouldn't try, but I will anyway: Web 2.0 is a commemorative coin minted in celebration of the end of the dot-com crash. Like all commemorative coins, it has no actual value.

( Aside: it's rants like these that are probably the only reason I still read DDJ anymore )

As I've talked about in the past, we were doing the whole browser-as-rich-client thing back in 2000 (like many others). It was easier for us to innovate then because we were working in a closed environment. We had control over the browser and we knew we could rely on fat pipes between the server and client. That is now known, of course, as AJAX - a key element of most "Web 2.0" definitions and another just awful term that really missed the point. What is relevant about AJAX is not the Javascript and the XML, but the experience. Those specific technologies just happen to be a means to that end.

A little anecdote: I remember vividly a brainstorming session (for lack of a better word) I had with my father back in 1997 while visiting the college I eventually attended. We came up with some pretty cool ideas, and yet we summarily dismissed most of them as too unrealistic and "out there".  After all, could you imagine having to convince those offices to get a computer and - gasp - dial in for Internet access all day?

The reason I'm so excited now is because all the innovations in connectivity, hardware, and - perhaps most importantly - de-facto standards (like, say, RSS) have eliminated many of the constraints we once operated under.  It means we can move beyond the technical limitations that dictated how once did things and instead focus on the problem itself.  Where we were once concerned with whether a business would have a computer and an Internet connection, we now have always-on, high-speed connections in our pockets.

Of course, just because we can do something doesn't mean we should.  In my opinion, we went too far with a lot of the Javascript / Web stuff I mentioned previously. A lot of really was innovate, but some of it really didn't make sense either. After 4-5 years of doing everything in the browser, the pendulum finally started to swing back for us internally. That is, we finally realized that, hey, maybe data entry is better off in a desktop application than a web browser. We finally recognized that certain tasks are better suited in different contexts.

Paul Graham made this point nicely in his requisite "Web 2.0" article:

The fact that Google is a "Web 2.0" company shows that, while meaningful, the term is also rather bogus. It's like the word "allopathic." It just means doing things right, and it's a bad sign when you have a special word for that.

The revolutionary stuff does not happen when we do the same old thing in a new container. The revolutionary stuff is when we have ubiquitous access to our information and can interact with our world from any context we happen to be in - and with an experience scaled appropriately for that context. In other words, the experience should be different on a mobile phone than it should be on your beefy desktop with 3D graphics, 2GB of RAM and a speedy connection.

Don't worry, I'm not going to exercise my namesake privilege and invent a new Web. But if I were, I would define it as a world where the lines blur and boundaries are eliminated.

Only published comments... Feb 10 2006, 09:18 AM by Tim

View related posts

 

Kevin Heller said:

So we're are we on the spectrum from web 1.0 to 2.0? If such an analysis could be made?
February 10, 2006 12:33 PM
   

Tim said:

Tough to say. I think we have a long way to go to realize the value of all this, but I think we're at a point where a lot of the pieces are in place.
February 13, 2006 6:34 PM
 

Josh Einstein said:

I'm fed up with "Web 2.0", Ajax, and all these other goofy things like del.icio.us. Nothing frustrates me more than when people start talking about these disparate web toys that are going to replace Office (or even Windows!). Why do I even know about the site 30boxes.com? Because it uses Ajax and a bunch of bloggers talked about how hip it was because it's "Web 2.0". It's not even as functional as Palm's version 1 desktop application that came free with US Robotics Palm pilots!

I am just growing increasingly annoyed with the notion that web pages can replace desktop applications. And I say this as someone who has watched the pendulum swing back and forth several times between "all on the server" and "all on the client". Every few years, one or the other is the next best thing.

Sorry this wasn't a rant at you!
February 14, 2006 6:24 PM
   

Tim said:

I don't disagree with you. In fact, that's exactly my point - web pages can replace desktop applications, but only in specific situations. We shouldn't look to move the desktop wholesale to the browser, but rather identify where it makese sense to allow access via the browser.
February 14, 2006 8:01 PM
 

Mads Kristensen said:

Hi Tim. Thank you very much. I mean that. I've had big discussions about this particular subject, and it seems that only developers agrees with yours and mine take on the matter. I'm just glad to have read your article, because then I know that at least one more agrees with me :-) Nicely written by the way. Thumbs up.
March 14, 2006 2:47 PM
 

Loosely Coupled // Tim Marman's Weblog said:

There has been a bit of controversy over O'Reilly's "Web 2.0" service mark cease-and-desist letter and...
May 26, 2006 2:30 PM
 

Loosely Coupled // Tim Marman's Weblog said:

It's become obvious that people really don't "get" AJAX, but then I guess this is the problem with buzzwords. ...
June 8, 2006 7:16 PM
 

Loosely Coupled // Tim Marman's Weblog said:

As I've written in the past, I'm not a big fan of buzzwords because "they're vague, overbroad, ill-defined,

October 10, 2006 12:23 PM
 

Loosely Coupled // Tim Marman's Weblog said:

As I've written in the past, I'm not a big fan of buzzwords because "they'revague, overbroad, ill-defined,

October 10, 2006 12:23 PM