What it Means to be a Mashup
An anonymous reader writes "IBM DevWorks has provided us with an introductory article that helps define what it means to be a mashup. In addition to just defining what a mashup really is the author also delves into what they do for the community at large and where they may take us in the near future. From the article: 'Mashups are an exciting genre of interactive Web applications that draw upon content retrieved from external data sources to create entirely new and innovative services. They are a hallmark of the second generation of Web applications informally known as Web 2.0.'"
This is possibly the most vague article I have ever read.
I didn't manage to learn any more from this article that the Slashdot summary didn't provide.
Although there are sections describing what each tehnology is, and how it would be used, the summaries are vague, and lack any real content. I have written similar non-technical summaries for executive types, and it looked vaguely similar to this.
Reading the README of any AJAX application will tell you 80% of what the IBM article goes into.
The only information I can as being useful is the resource list cited at the end of the article.
Signature v3.0, now with 42% less memory usage.
How did they manage to cram so many buzzwords into one summary?
Take 2 dot-com like things with no real business model and put them together?
Web 2.0! Bubble 2.0! Crash 2.0! Recession 2.0!
Enough with the 2.0 already.
- Adam L. Beberg - The Cosm Project - http://www.mithral.com/
This article is clearly nothing more than an attempt to get us all complaining about how much we hate buzzwords, and the concept of Web 2.0.
... is a cannabis smoking session. Though having met a few web developers in my time perhaps IBM they chose the right name after all!