Maggie Tsai's Bookmarks tagged ajax →  View Popular

harnessing collective intelligence

it does seem the social aspect of Web 2.0 is the the biggest roadblock for acceptance with technical people in the software industry. 

Web 2.0 is not a technology, it's a way of architecting software and businesses. 

The disconnect between the technicians and the architects and CTOs  seems to come particularly from the social aspect of Web 2.0.

Web 2.0 is really a set of related forces, design patterns, and business models that are increasingly emerging onto the world stage.

the shortest definition that works for me is that "Web 2.0 is made of people

importance of user ownership of data.  The centrality of the user as both a source of mass attention (over a hundred million people, probably 2 or 3 times that many, are online right now) and an irreplaceable source of highly valuable data, generally encourages that the user be handed control of the data they generate.  If control over their own attention data is denied them, they will just go to those who will give them that control.  This gives some insight into the implications of Web 2.0 concepts, which were mostly gathered by examining prevailing trends on the Web.  Forrester is calling the resulting fall out of these changes Social Computing and it'll be interesting to see what the effects of the widepsread  democratization of content and control will ultimately be a generation from now

People are very tired of synchronizing their data between work, home, and family computers, upgrading and patching their software, and worrying about security and backups.  Ajax has been a force here (covered here in my popular State of Ajax) by allowing the creation of online software that is as good as native software (yes, a few limitations still exist, but can increasingly be worked around).  Ajax is much more powerful because its connected status: it can reach people and information around the world. 

An Increasing Attention Scarcity:  There isn't enough atttention, or users that supply it, to go around.  Particuarly there's just too many channels vying for it or existing channels are still dominate the majority of attention.  This will affect the viability of new online entries and force them to create innovative ways to acquire attention.
- Online Social Communities Are A Winning Model - It's unclear what the monetization is (other than advertising) or the cost of successfully starting one, but many of the fastest growing and most popular places heavily use social software techniques to draw and keep users.  And some begunnung are to acquire valuations in the billions.  (Some Examples: SecondLife, MySpace, FaceBook.).
- The RIA Model Works - The term Ajax was just coined in February of last year, but it looks like it's here to stay and then some.  Using nothing more than what you find in the browser, Ajax can create great Web platform ready clients that are as good as native clients.  To see the potential, check out the radically advanced Hive7 using nothing more than Javascript.  Expect that XUL, WPF/E, and Flash will give Ajax a bit of a run for its money later this year though.
- The Mashup Phenomenon Will Mature or Wane - Part of the problem appears to be the tools but also the usefulness.  Most mashups aren't more than a feature or two.  More sophisticated ones are coming, but if compelling mashups don't materialize in bigger numbers,  the technique could lose mindshare as a model for building composite online software made up from the services of multiple Web sites.
- Traditional Software Vendors Will Struggle in a Web 2.0 World - Microsoft and Google will likely figure it out, though it's not a sure thing either..  Microsoft has serious product line baggage and Google has healthy challenges in managing its growth and maintaining a sharp focus on strategy.  Google's latest products don't seem to have their famous edge, for example.  The smaller, nimbler Web 2.0 startups might continue to be a great source of innovation but it might make sense for Google to acquire startups and  immedatiely spin it off to avoid the "big company effect."

Many a year ago, Jeff Rouyer won the Netscape DHTML competition with his flying dude interface and put DHTML on the map. The winning entry, apart from being 3D in design which up until that point had not been seen on the Web, also had something that was quite uncharacteristic of Web pages.

Not long after that, he thought of the idea of using an IFrame technique where content would be loaded into a hidden IFrame and then sucked back out and into a div element. This was the genesis of what today is known as Remote IFrame Scripting. Remember we are talking close to a decade ago which is a good indicator of how far ahead of the curve Jeff was at the time.

Unfortunately, the traditional design documents don’t always save us time or money. In some cases, they’re actually more expensive because they fail to accurately account for all of the factors involved in building a Web application. Additionally, due to the static nature of the documents, they present a challenge when representing highly dynamic pages that rely on DOM scripting and AJAX.

Lightbox JS is a simple, unobtrusive script used to overlay images on the current page. It's a snap to setup and works on all modern browsers.