Once upon a time, web pages were just text, written in something called “Hypertext Mark-Up Language” or HTML. This is a code that makes much use of angle brackets, quotation marks and forward slashes. When your computer requested a web page from a site, the site sent back the text file then your web browser program parsed the angle brackets and the other gobbledegook in order to render it for displaying on your screen.That was the state of the technology in 1993. In 1994, Brendan Eich, a programmer working for Netscape, the first browser company, had the idea of embedding in a web page mini-programs (called scripts) that a browser could run as it was rendering the page. This would enable the creator of the page to build in all kinds of useful functionality.
http://www.guardian.co.uk/media/2009/jun/07/media-business-google-waveAlso see:Debating the power of Google’s Wave
We’ve had about a week to absorb the Google’s pitch for Wave, its new experimental communication platform, and about a day to try the actual early “sandbox” build of the service. See our hands-on review. But there’s more to talk about with Wave. It’s not just an app, it’s an important evolution in the philosophy of written communication.People will see Wave in different ways. For some, it’s a clever take on e-mail. Others will see it as instant messaging with new features. Developers will look at Wave’s open specs and APIs, and see a framework for new collaborative apps. But is it really any of these things, or just a crazy experiment from Google’s Australian outpost?
http://news.cnet.com/8301-17939_109-10256471-2.html
Leave a Reply