When I first heard of the web in ’95, I thought a lot about the consequences of networking the computers sat on every desk. I heard talk of how that virtual-proximity would remove barriers to information-flow and leverage many hands to make light work of large problems, how new communities would form and ideas be exchanged. All of this was true but not nearly as much I expected.
For most people, the true potential of online communities is something they read about only in the Sunday newspapers. Dave Winer may be sought out by readers in every village he visits but for most people it takes years to reach out in even a city and retirees and young mothers find themselves sometimes unbearably lonely once isolated from those physical networks.
For the majority of people, the human-networking potential of Web1.0 never emerged. Everyone uses the web but ask most people what they do with it and they’ll tell you that they use it for shopping, email, research and news. For the man in the street, the internet revolution was arguably less of a revolution than an evolution.
Web1.0 explored what was possible when we took out the human middle-man and allowed our computers to connect direct to computers and data in other networks. It was about what became financially and technically possible when we no longer needed a remote operator in order to interface with a remote machine or a physical network to deliver remote information.
That’s not to say that machines couldn’t communicate before ‘95. Be it counting handle-turns or pulses of light, machines have always had a language of interaction. Nonetheless, the creation of one common language (or triumvirate of languages) lowered the barriers sufficiently to mean more people and machines chose to connect. At the same time, servers allowed those machines to safely expose useful data from their vulnerable interiors to the world at large. More information and lower barriers created more entrants, more entrants created more still and Web1.0 cascaded into existence.
Humans have always been able to communicate and network but when we look to our virtual networks, the lockin of email and the hassle of publishing and reading has kept most of them ultra-private and defensive. Those defence mechanisms are so strong we will sooner reject an email from a friend than let risk spam and even when we want to, we will sooner sit in alone and in silence than chance an interaction with a stranger.
Humans are the network that Web2.0 connects and RSS is the common language. RSS is to conversation what TCP/IP was to data and blogs are to humans what server-software was to computers. We have always been able to communicate but RSS makes it that little bit easier and more reliable. RSS lowers our threshold to reading and hence raises our audience for writing whilst blogging allow us to put a little bit of our sensitive data outside our personal firewalls and to give others something to interact with. We all start to realise that giving a little of ourselves can bring far more in return. More interaction breeds more ideas and RSS and aggregators give those ideas a network they’ve never before known.
TCP/IP was DNA for data on a network, it charted its delivery and guaranteed its integrity. XML and RSS are fast becoming the DNA for ideas on a network. Words become nucleotides, items become genes and just as with real genes, we are the vehicle to take the best of them to the next generation. Some survive, some multiply, some will be lost and some will never get read but one way or another, RSS lets them evolve faster than fruit flies.
The blogosphere is the detailed transcription of an entire population’s intellectual DNA, an exhaustive textual, audio and video description of the ideas and emotions of a community. The blogosphere and what it will evolve into become not just the zeitgeist but the very definition of the human state. If the handbook for the revolution is Surowiecki’s excellent “The Wisdom of Crowds” then note that the blogosphere is the crowd - ignore its wisdom at your peril.
Where Web1.0 allowed us to connect to remote computers without an analogue call centre worker, Web2.0 allows us to connect to remote people without an analogue journalist. Despite what’s bandied around this don’t mean we’ll dispose of all journalists and publications any more than online news meant we disposed of newspapers. There will be change for sure but good journalists add value far beyond the information they transcribe and those who think it’s all change are more naïve than those who believe it’s none.
Some argue that Web2.0 really isn’t an event - it’s incremental and undeserving of a name. In some ways they’re right. 2005 and “Web2.0” isn’t where rich human networking started any more than 1995 and the “Information Super-Highway” were where computer networking started.
“Web 2.0” applications were around long before today. EBay was 2.0 and so were Citeseer, Friends Reunited and P2P. Spam email may have been 1.0 but the “I love you virus” is 2.0. Amazon isn’t a 2.0 company but its reader reviews were. Page rank wasn’t a Web2.0 application though auctioning Adwords certainly was.
So what is it that makes Web2.0 a big deal? It’s a big deal because people say it’s a big deal. Lots of people. Lots of people are blogging, lots of people are tagging and the number grows almost exponentially. When a lot of people do something one month and twice as many people do it the next month, it makes it a big deal. The participation in Web2.0 has grown well beyond the founders-circle and shows no signs of slowing down.
And why give it a name? Well when lots of incremental things start happening in a short space of time and when those incremental things build into a qualitative change of state we need a way to distinguish the new one from the old one. Web2.0 seems a very apt descriptor for where we are about to arrive.
Tagging and blogging are the poster children of 2.0 and it’s interesting that many still dismiss them as they dismissed the directories and homepages of ’94. A few years ago they would have been credible. Not today though. Today there is too much noise from too many directions and too many demographics.
The bloggers of today aren’t scouts looking for water and flatlands, those pioneers came and settled back in the late nineties. Those that you see now are the forward party of a full blown caravan and land is being settled. There’s a city being built and I imagine that anyone who doesn’t settle right now will soon be unable to afford the land they stand on.
Web 1.0 was about connecting machines. Web 2.0 is about connecting humans. For my money, when it comes to interaction, human beats machine every time and my work, my emotions and my livelihood are all staked on Web 2.0 being a very Big Deal.


9 comments:
I am in agreement with Wired Magazine's Kevin Kelly that in the near future, the Web will become our operating system and most applications will run on the Web 2.0. Indeed, it is only a matter of time before someone writes a full-featured spreadsheet (like Microsoft Excel) for the Web. From there, the sky is the limit.
I have actually seen a commercial AJAX spreadsheet but can't remember for the life of me where I found it. There is however another non-commercial implementation here.
I'm certain that now that much the javascript snobbery has passed, we are only going to see more serious applications being deployed.
I would also not be surprised if we start to see a resurgence in Flash. I chose to develop with AJAX because of its CSS and document support but I actually think that Flash is still the best platform for rich web apps. If you're looking for a ubiquitous cross-OS *and* cross browser platform I don't think there's anything that can currently beat it.
Secondly, the collaborative and open source nature of the emerging Web 2.0 requires the ability to easily link to all data. Linking to a particular portion of a Flash application is (afaik) not possible.
The Web 2.0 will maintain better cross-os and cross-browser compatibility due to the tight standards being developed by the w3c. The compatibility issue will disappear, not because of a "holy grail" language that solves the problem, but because the standards organizations will help create open languages (like XML) that eliminate the issues.
I am concerned that Web 2.0 will become *too* self-contained, which is not the ultimate goal of the semantic web.
I'll keep you posted on my Web os project.
My opinion is that a true Web 2.0 application contains a mixture of both trends.
Do you agree?
1. Does the encapsulated nature of a flash app defeat the purpose of an open-source web-service model?
I think it's important to distinguish between the remixability of the tools and the accessibility of the data. Both are useful but only one is critical. As long as you can get access to the raw data and the processing logic is clear then the application/front end is academic. You don't need me to build my blog using an open source tool you just need to know my webpage is HTML/CSS and my feed is RSS. It doesn't matter that Flickr use Flash for their slideshows as long as the raw data is accessible via HTTP.
2. Do non-standards based approaches (like Flash) undermine W3C efforts
IMHO standards are a means to an end rather than an end in themselves. Using standards is only useful to the extent that it results in a better system. If a flash app is better then it's better, standards or otherwise. I do agree that you're more likely to get a good app by making it remixable (tho I'm not sure that view source isn't now possible in Flash).
I develop using standards because I know that's going to result in the largest audience and because generally the standards will be better thought out and ultimately more viable than their proprietory contemporaries (not always true though - remember the CSS box model - MS's interpretation was far more helpful than the (sadly standard) W3C. XMLHttpRequest was also a non-standard MS creation). However, if I build a graphing tool, or a media player into my rich app I'll be using Flash. SVG and it's ilk just aren't mature enough or supported enough to be of any use but believe me I'd be over them like a rash if they were.
A thought... standards are useful because they result in something being behaving the same regardless of implementation, right? ECMA script is still significantly different from browser to browser and only active in about 90%. Flash is the same in all browsers and active in over 97% of them - which one's more standard? (I'm starting to sound like a Flash fanatic here. I'm really not I just think it's important to use the right tools for the job and like javascript 12 months ago, I don't feel Flash gets the credit or the use it deserves).
You said that the compatibility issue will disappear but I'm not sure that that's true because we'll always be moving forward. The standards issues of today aren't the same as those of five years ago and whether it's the box model, SVG, BitTorrent, VOIP or 3D, I think there's always going to be a standards issue of the day in the future.
3. If we can't link to a page then aren't we breaking the web?
A webpage is just an interface to data. Up until recently they've mostly been static and the data/interface have been fused together but now that's starting to change. It's the data we want to link to rather than the interface and when the two begin to uncouple we have to rethink some of our assumptions (i.e. that interaface==data).
If you're providing rich data driven apps then your application has a 'state'. That state might describe multiple windows and relationships with multiple data sets. Does it make sense to create a link to what you're doing in outlook or photoshop or a link to your current desktop state in windows? We will always want to be able to link to data but I'm not sure that linking to the interface (which is all a webpage is) will continue to make sense.
4. Do I think that Web2.0 is about a mixture of thin-client apps and interconnectable data?
Yes, absolutlely, I think this is the ninja duo but I also think it's two sides of the same coin. I do agree that these seem to be two of the main thrusts of 2.0 but I see the two as inextricably linked. I see that the AJAX apps are ultimately going to find their fit as the interface to to web-service data (or maybe that's just mine ;). If you look at them then the RSS feeds that have been built into the 37signals products and Flickr are in fact exactly the first signs of this. We're seeing most products starting to do RSS-out, perhaps the next wave of interest will come from RSS-in?
Ok, so I wrote more than I possibly intended to but you managed to push a lot of my buttons. I'm sure that this has pushed some of yours Nick, tell me what you think....
Yes, Web 2.0 is a very interesting topic. You make some interesting points.
Due to the complexity of the comments and my need to elaborate, I feel it would be best to add my rebuttal to a new post on my website. I'll keep you posted when I finish writing the essay.
I couldn't wait to write some of my thoughts about this....
I'm glad you mentioned Flash as a development tool for creating rich internet applications because I hadn't considered it.
I've been researching and it's very interesting to note that the Flash people are doing almost the same things as the AJAX people right now.
Some examples of AJAX and Flash RIAs (notice the similarities):
AJAX weather widget:
http://openrico.org/rico/demos.page?demo=ricoWeather.html
Flash weather widget:
http://www.laszlosystems.com/demos/weather/
And it doesn't stop there....
AJAX shopping cart:
http://projects.backbase.com/RUI/shop.html
Flash shopping cart:
http://www.laszlosystems.com/lps/sample-apps/amazon/amazon2.lzx?lzt=html
--------
While we’re mentioning accessibility to data and applications, we shouldn’t overlook accessibility to development platforms.
Check out the requirements for Laszlo development:
Java SDK (approximately 50mb)
OpenLaszlo development kit (approximately 50mb)
And the requirements for AJAX development:
A web browser and a download of a few Javascript source files (no less than 500k). Also Windows Notepad (or simpletext if you're a Mac user).
While the accessibility of development tools doesn't necessarily tell us which tool will become the accepted standard, it is an interesting fact to note.
Furthermore,
here is an application using both Flash and AJAX
I found little to disagree with in your comments. I think that the choice of development platform comes down to personal preference. Javascript and Flash both use XML. Javascript and Flash both have a chance of becoming development platforms for the next evolution of the Web. Indeed, perhaps Javascript and Flash will meld into a development platform that surpasses both in data accessibility and processing muscle.
AJAX weather widget
Flash weather widget
AJAX shopping cart
Flash shopping cart