Showing posts with label marc andreessen. Show all posts
Showing posts with label marc andreessen. Show all posts

03 March 2009

CollabNet Comes Out of the Shadows

CollabNet has a fascinating history that goes back to 1999, when Collab.Net launched SourceXchange:


a site where companies can post proposals for programming work and solicit bids from open source coders. It is intended to form the first of a series of projects exploring new business models based on open source, and which collectively make up Collab.Net. A list of those involved reads like a roll call of the leading players in the open source industry. Employees include Frank Hecker, who played a major role in convincing Netscape to take its browser open source, and James Barry, who helped convert IBM to Apache. Alongside [co-founder Brian] Behlendorf, Tim O'Reilly and Marc Andreessen are board members, and investors in a $35 million round of funding closed in June 2000 included Dell, HP, Intel, Novell, Oracle, Sun and TurboLinux....

On Open Enterprise blog.

31 October 2007

Google's OpenSocial

Or should that be Open Social? - That's what a certain Marc Andreessen (now, where have I heard that name before?) calls it, and he should know:


My company, Ning, is participating in this week's launch of a new open web API called Open Social, which is being spearheaded by Google and joined by a wide range of partners including Google's own Orkut, LinkedIn, Hi5, Friendster, Salesforce.com, Oracle, iLike, Flixster, RockYou, and Slide.

In a nutshell, Open Social is an open web API that can be supported by two kinds of developers:

* "Containers" -- social networking systems like Ning, Orkut, LinkedIn, Hi5, and Friendster, and...

* "Apps" -- applications that want to be embedded within containers -- for example, the kinds of applications built by iLike, Flixster, Rockyou, and Slide.

This is the exact same concept as the Facebook platform, with two huge differences:

* With the Facebook platform, only Facebook itself can be a "container" -- "apps" can only run within Facebook itself. In contrast, with Open Social, any social network can be an Open Social container and allow Open Social apps to run within it.

* With the Facebook platform, app developers build to Facebook-proprietary languages and APIs such as FBML (Facebook Markup Language) and FQL (Facebook Query Language) -- those languages and APIs don't work anywhere other than Facebook -- and then the apps can only run within Facebook. In contrast, with Open Social, app developers can build to standard HTML and Javascript, and their apps can then run in any Open Social container.

What this shows, for the nth time, is that the future history of computing is about the race towards openness, and that the company that opens up the most - as in totally - wins. Google seems to get that, even if there are still a few dark corners of its soul that could do with some sunlight.