Everyone loves open source - well, everyone apart from Microsoft, that is. The only problem with open source is deciding how much code control you're willing to relinquish, especially when open source puts your precious bits and bytes - and ultimately your own product plans - into the hands of your competitors.
Adobe Systems' Flash has long dominated PCs and the web, but the company has been under slowly mounting pressure to open source the player's source code.
This came to a head recently when Dion Almaer, co-founder of Ajaxian.com and Google's open web advocate, delivered a talk on the state of AJAX at Google Developer Day in London. I asked Almaer why Google makes little use of Adobe Systems' Flash, YouTube aside, and he gave a forthright answer.
Flash is not "open enough," he said, explaining that the Flash player is not open source and its development is not driven by the community. Google likes the technology, he added, and its closed-source status is a matter of ongoing discussion.
I put this to Dave McAllister, Adobe's director of standards and open source. "Dion and I have exchanged opinions about this," he said, adding that "there are constant discussions with Google," though he could not confirm any on this specific matter.
McAllister noted the SWF format for compiled Flash content is an open specification and that the Flex Software Development Kit (SDK) for building Flash content is open source, but said there is little prospect of open sourcing the player itself.
"Sixty-five per cent of the code is not owned by Adobe," he claimed. "We spend an incredible amount of money to license audio and video codecs that we then give away for free. If we open sourced the code of the Flash player, we would immediately fragment the video runtime market, because we can't give away those codecs."
McAllister rejected Almaer's point about the community, saying there is "peer participation, a visible roadmap, open bug bases, and open discussion between engineers and developers...the only open source principle that doesn't get communicated is the actual source code." Ah.
Haven't we been here with Sun Microsystems, before it eventually open sourced Java?
McAllister was dismissive of the comparison.
"The lesson learned from the Java exercise is that a marketplace that is losing speed can attempt to regain some of it from open source. We can certainly learn from [Sun] that it's very easy for competitors to sabotage your own efforts," he said.