Group items tagged

IntalioCloud takes on Salesforce.com with public-private cloud design. Note that business applications developed for use in Salesforce's platform have to use the company's proprietary programming language, while IntalioCloud is open to many languages such as JavaScript and Ruby. Third, Intalio says it provides 25 gigabytes of data storage per account, much more than Salesforce. $42 Mill in VC The nexxus here is that both salseforce.com and Intalio need to provide integration into the MSOffice productivity environment to compete with Microsoft Azure.

This document discusses the primary reason ODF failed in Massachusetts: compatibility with the MSOffice productivity environment, and, the billions of binary documents in use by MSOffice bound workgroups and the business processes so important to them.

Microsoft has announced the next generation of MSOffice, and it turns out to be SharePoint at the center of the deep connected MSOffice "rich client" desktop productivity environment, and, an online Web version of MSOffice. Who would have guessed that one of the key features to MOSS would be universal accessibility to and collaboration on MSOffice documents - without loss of fidelity? No doubt the embedded logic that drive BBP's (Bound Business Processes) is also perfectly preserved. Excerpt: "Office Web Applications, the online companion to Word, Excel, PowerPoint and OneNote applications, allow you to access documents from anywhere. You can even simultaneously share and work on documents with others online," Microsoft says on its Office 2010 Technical Preview site. "View documents across PCs, mobile phones, and the Web without compromising document fidelity. Create new documents and do basic editing using the familiar Office interface."

Link is the latest version link so page should update when this specification graduates to a W3C recommendation.

We can all learn a lot of lessons from the history of DDE/OLE/ OLE3/COM /ActiveX/DCOM /COM+ (you can start reading up on Wikipedia to get some background) and how we went from everyone using best-of-breed standalone apps to one integrated, nearly monolithic Office. It basically all started with copy and paste. People who never spent a lot of time in singletasking, character-mode operating environments like the DOS command line don't recall that simply copying-and-pasting information between apps was difficult at the time. And part of the revelation of Windows for mainstream users (or Mac, for leading-edge tech fans), was being able to easily share data in that way. This was different than what Unix users were used to with the command-line pipe, or from what most applications do with feeds today, in allowing structured information flows between applications. There's a desire to combine data from different sources in an arbitrary way, and to have the user interface display the appropriate tools for whatever context you're in. The dominant model here, probably because of the influence of the early PARC demos, is to have toolbars or UI widgets change depending on what kind of content you're manipulating. Microsoft was really into this in the early 90s with OLE2, where your Word toolbars would morph into Excel toolbars if you double-clicked on an embedded spreadsheet. It was ungainly and ugly and slow, especially if you had less than an exorbitant 8MB of RAM, but the idea was pretty cool. And it still is. People are so focused on data formats and feeds that they're ignoring consensus around UI interoperability. The Atom API and Metaweblog API give me a good-enough interface if I want to treat a discrete chunk of information (like a blog post) as an undifferentiated blob. But all the erstwhile spec work around microformats and structured blogging (I forget which one is for XML and which one's for XHTML) doesn't seem to have addressed user experience or editing behavior

Google has been making a number of acquisitions that are clearly Docs-related. Over the weekend, TechCrunch reported that the search giant is in the final stages of talks to acquire DocVerse, a startup that lets users collaborate around Office documents, for $25 million. The deal would also bring Google some key hires, since the startup's co-founders were managers on SharePoint, Microsoft's popular collaboration service. This follows the November acquisition of AppJet, a company founded by former Googlers that created a collaborative word processor. (It's worth noting that Google Docs itself was the offspring of several acquisitions, including Google's purchase of Writely.) Meanwhile, Google has been talking up the splash it wants Google Docs to make in 2010. Don Dodge, who just made the move from Microsoft to Google, recently told me, "2010 is going to be the year of Gmail and Google Docs and Google Apps." Even more concretely, Enterprise President Dave Girouard said last month that Docs will see 30 to 50 improvements over the next year, at which point big companies will be able to "get rid of Office if they choose to." Presumably features from AppJet and DocVerse will be among those improvements. I'd certainly be thrilled to see the battle between Office Docs become a real competition, rather than upstart Google slowly chipping away at Microsoft's Office behemoth.