Future of the Web

Yup. They're making noises about moving Flash and AIR into ARM-based appliances. This seems a sound strategic move for Adobe in response to Silverlight, drilling hard for the big computing market that already dwarfs the desktop computer market. It ain't just about the desktop and the Web anymore, folks.

Adobe positioning AIR for a move into embedded systems? E.g., from Wikipedia: "Because of their power saving features, ARM CPUs are dominant in the mobile electronics market, where low power consumption is a critical design goal. Today, the ARM family accounts for approximately 75% of all embedded 32-bit RISC CPUs, making it one of the most widely used 32-bit architectures. ARM CPUs are found in most corners of consumer electronics, from portable devices (PDAs, mobile phones, media players, handheld gaming units, and calculators)." Don't miss page two of the linked article.

This planning document forms the basis for the forthcoming work to develop European Interoperability Framework v. 2.0. It is the overview of things to come, so to speak. Well worth the read to see how SOA concepts are evolving at the bleeding edge. But also noteworthy for the faceted expansion in the definition of "interoperability," which now includes: [i] political context; [ii] legal interop; [iii] organizational interop; [iv] semantic interop; and [v] technical interop. A lot of people talk the interop talk; this is a document from people who are walking the interop walk, striving to bring order out of the chaos of incompatible ICT systems across the E.U.

Full disclosure: I submitted detailed comments on the draft of the subject document on behalf of the Universal Interoperability Council. One theme of my comments was embraced in this document: the document recognizes human-machine interactions as a facet of interoperability, moving accessibility and usability from sideshow treatment in the draft to part of the technical interop dimension of the plan.

As the economy tanks, open source proponents reflexively point to the low capital costs of acquiring open source software. But big customers want more than a bargain. They also want better. Thus, collaboration is more than just staying true to the open source credo of community and cooperation. It's also a smart business move. Drupal and Alfresco show us why.

The author clearly missed that Sun is a full-fledged Microsoft partner and that StarOffice 9, of all OpenOffice.org clones, is the only one that has write support for both ODF v. 1.2 and ODF v. 1.1, the latter of which is the only ODF version being implemented by Microsoft. The other OOo clones write only to ODF 1.2, which is dramatically different from ODF 1.2. So StarOffice will almost certainly have better interop via ODF with MS Office 2007 than will OOo 3.x or Lotus Symphony. For $25 per seat in the enterprise, $34.95 retail. The author simply misses that "pretty much the same thing can [NOT] be had for nothing from OpenOffice.org." There is a method to the claimed Sun madness, methinks. IBM gets left standing at the altar again.

The nine essential considerations of cloud computing. This may be the best article yet written about cloud computing. A must read! ,,, ""What sort of cloud computer(s) should we be building or expecting from vendors? Are there issues of lock-in that should concern customers of either SaaS clouds or PaaS clouds? I've been thinking about this problem as the CEO of a PaaS cloud computing company for some time. Clouds should be open. They shouldn't be proprietary. More broadly, I believe no vendor currently does everything that's required to serve customers well."

Non Microsoft XPS Viewer! I blew up my machine twice trying to install Microsoft's XPS Viewer. The Software Imaging version flew right thru, and works like a charm. Recommended for those having problems with XPS formats.

Superficially, this sounds like an application of the principles won by DG Competition in the Court of First Instance's Commission v. Microsoft interoperability decision. But note that here we deal with an investigation into deliberately-created interop barriers rather than those maintained by withholding full communication protocol specifications from competitors. Notice that the investigation encompasses throttling of internet connections for particular uses, an increasingly common practice by Comcast and other ISPs in the U.S., where both VOIP and P2P file-sharing are targeted uses. E.U. and U.S. antitrust law are similar, as efforts to harmonize antitrust law on both sides of The Pond are now decades old; this move does not bode well for bandwidth throttling in the U.S., particularly when aimed at throttling competition. It takes no giant mental leap to apply such principles to big vendor-dominated IT standards bodies that deliberately create or maintain interop barriers in data format standards. Indeed, DG Competition Commissioner Neelie Kroes has already served notice that interop barriers in standards-setting is an item of interest.

By enabling human collaboration and innovation on a scale never seen before, Web 2.0 is becoming Enterprise 2.0. Here's why no business will be left untouched. (This eBook is filled with stats, projections, and analysis)

While the last decade was focused on the Web, the next phase in the evolution of our industry will be on the convergence of Web, mobile and desktop applications and the ability to extend existing applications with these new technologies for a consistent user experience regardless of how and where the information is viewed,' says Nexaweb CTO Jeremy Chone

Response from Microsoft's Dare Obasanjo to the Tim Bray blog: Get in the Cloud. .. "When it comes to cloud computing platforms, you have all of the same problems described above and a few extra ones. The key wrinkle with cloud computing platforms is that there is no standardization of the APIs and platform technologies that underlie these services. The APIs provided by Amazon's cloud computing platform (EC2/S3/EBS/etc) are radically different from those provided by Google App Engine (Datastore API/Python runtime/Images API/etc). For zero lock-in to occur in this space, there need to be multiple providers of the same underlying APIs. Otherwise, migrating between cloud computing platforms will be more like switching your application from Ruby on Rails and MySQL to Django and PostgreSQL (i.e. a complete rewrite)...." Although cloud computing vendors are not explicitly trying to lock-in customers to their platform, the fact is that today if a customer has heavily invested in either platform then there isn't a straightforward way for customers to extricate themselves from the platform and switch to another vendor. In addition there is not a competitive marketplace of vendors providing standard/interoperable platforms as there are with email hosting or Web hosting providers.

Excellent overview of where applications are going. Richard Monson-Haefel, (whom i met at the 2008 Web 2.0 Conference) explains the convergence of four emerging application models: Web Clients (Browsers), RiA Clients, Client/Server, and Widget Engines. He comes up with a convergence point called "Fit Client", offering Adobe Air as the leading example. Richard walks through each application model, discussing limitations and advantages. Good stuff, especially this comment: "The widget engine is really a wonderful architecture that gives you the power of the desktop (via the widget engine) and the management of the Web (via widget downloads).  Widget engines can out-perform RIA solutions and they can store larger data sets.    The limitation of Widget engines is not in their architecture, it is that they have been designed for applications with fairly weak capabilities compared to client/server. Widgets tend to be single-purpose applications with limited access to the native operating system. That said, the widget architecture itself - the separation of the platform from the applications - is important. It makes it possible to create applications (widgets) that are portable across operating systems and are packaged for easy download and installation. "

The computer desktop - as was the case with newspapers before there was radio and radio before there was television - has become the high ground from which empires are built. While dominance of the desktop has been maintained for the last decade or more by Microsoft, which at one point represented 95% of the desktops used by all consumers, the future is less certain.it will not be a single operating system that prevails. In the end it will be desktop runtimes that become the most important platforms A desktop runtime is a platform that provides a consistent runtime environment regardless of the underlying operating system. Desktop runtimes are already extending beyond their primary target platform, the desktop, to the Fourth Screen - smart phones.

In the future application developers won't care what desktop operating system you use, they will only care which Fit Client platform is the most pervasive. This is what Adobe AIR, Microsoft Silverlight, Google Gears and Curl are fighting for. Nothing short of the future of desktop and RIA development. Microsoft brings with it a huge ecosystem of .NET developers - potentially millions of developers already skilled in WPF, XAML and C#. That's a pretty scary for others in the Fit Client arena. Right now the future of the desktop is completely open. Anyone with enough clout could win the desktop - effectively usurping Microsoft Windows dominate position.

Last week, Microsoft reported that revenue from the Microsoft business division (MBD) grew 20% year over year to US$4.95 billion in the most recent quarter. That is more than Microsoft's client division, which makes Windows. Most of MBD's revenue comes from Office, though Microsoft doesn't break out an exact percentage. Windows has 1 billion users. Office has only 500 million. Consumers will be able to subscribe to Office Web and even get it at a discount price, provided they are willing to view Web ads. Business customers seeking "more manageability and control" will be able to buy subscriptions to Office Web similar to the subscription Microsoft offers for a bundle combining Web-based versions of Exchange and SharePoint. That costs $3 per user per month. Enterprises may also get Office Web through conventional volume licensing software contracts, which will allow them to either install Office on desktop and other client PCs, or have Microsoft host it on their server. Unlike non-Microsoft products (Google Docs - ZOHO - BuzzWord), Office Web will guarantee that the "viewing experience is fantastic" and that formatting and meta data from Office documents don't "get munged up,". Office Web will provide a superior "end-to-end solution" by letting users view and edit documents whenever they want to, including browsers such as Firefox, Internet Explorer and Safari and Windows Mobile smart phones. The Office Web focus will be on business productivity according to Chris Capossela. The Office Web experience can be enhanced by Silverlight (Microsoft RiA).