Programmable web

Ortiz (or ceo as he calls himself! ) says something important which I completely agree to and I am quoting him verbatim:

If you develop an application today, even a mobility application, very
likely it will have some components or functionality on the web. Design
your application with services in mind, services that are exposed and
consumed by your own products, and consumed by others who aggregate
your services with other services to build their core products, and in
turn expose their services for others to use. This philosophy is the
result of the social networking that is part of software development on
the new web – it is about collaboration, as this is best represented by
Mashups:

Mashup:

API X + API Y = mashup Z

Expose your services on the web using some well-understood
mechanisms such as REST, SOAP, XML-RPC, RSS, or simply using your own
HTTP-based protocol. Try to favor REST, SOAP or feeds. Always keep it
simple, but well designed, abstracted, decoupled, published, and
documented.

The return of the platform is pretty cool indeed. You can put
together a serious scalable application – let’s say for a demo of your
prototype, by using some core components that are available right now
on the web, some for free and some for a fee. Example of core services
that you can use now include simple queuing, simple storage, maps, searching, content sharing, and other APIs, from companies that include Amazon, Google and Yahoo!, and from the large number of Mashups – see The Programmable Web.

Just followed the programmable web link (this link is for the blog) and you see nice implementation of a sparkline giving stats on apis and mashups!