The death of the Web browser has long been predicted, and a recent report by Zapthink highlighted by Integration and Developer News and other outlets is calling today's browser-defined Web portals "wholly inadequate" for meeting the needs of today's increasingly sophisticated, standards-based content delivery mechanisms, Web services chief amongst them. The Zapthink paper sees these new capabilities creating demand for what they term "rich clients", a capability that falls between the "thin client" browser and the "thick client" locally installed software. This will not necessarily eliminate the browser-accessed portal, though, any more than automobiles eliminated the need for carriage houses: the technology changes, but the need for a familiar framework remains. What Web services' XML-based framework offers is the ability to deliver content in a way that's less rigidly coupled to a specific application's presentation of that content, enabling both browser-enabled delivery and delivery via more function-defined applications such as spreadsheets and word processing. These objects providing both content and functionality are key to the future of content for that very reason, providing the kind of useful and personalizable tools that people will want to have on their desktop for contextual use in a wide variety of settings and platforms. Content display application ju-jitsu will be an ongoing story over the next several years, but at the heart of it all will be the growing class of content objects that will be glad to oblige whoever satisfies the needs of a specific group of users most effectively.