Kevin Lynch Discusses Adobe's Approach to Openness

by Kristin Shoemaker - Sep. 25, 2008Comments (2)

eWeek has posted an insightful interview with Adobe CTO Kevin Lynch. Though Adobe's approach to open source wasn't the entirety of the piece, Lynch made several statements illustrating that he really understands -- and appreciates -- what opening code can bring to an application.

Some of Adobe's open source efforts may not feel as though they are coming fast enough, or even feel open enough, presently. But Lynch's explanations of Adobe's position on open source, and how it may be changing, seem logical and encouraging.

Of particular interest was Lynch's take on the opening of the Flash SWF format. Ten years after it was introduced, the licensing restrictions on SWF were removed and format was opened. The reasons Lynch gives for the format remaining closed for that long ("...the goal of that was to maintain consistency of the runtime.") or for the decision to open it ("We're doing that to increase confidence in relying on Flash around the Web...") may seem like Lynch isn't giving the whole picture. And he probably isn't.

His next statement, though, drives home that Adobe understands not only the proprietary, closed-source business model, but also that open source contributions and developments are potentially strong, viable competition. The beauty of it is that Lynch doesn't propose squelching this competition. He welcomes it as an opportunity, an incentive for Adobe to stay motivated and innovative:

But our hope is that there won't actually be a proliferation of many Flash players because that will really make it difficult for people to rely on the consistency that we've brought. So we're going to keep focusing on making an incredible Flash player and innovate on that.

This is how it should be. The format is open, and it is an opportunity for everyone involved. Lynch doesn't deny there may be better Flash players, but that's not something that Adobe can (or should) control. It is now about producing the best product they are able to in order to keep up with the offerings others are able to (finally) supply.

Lynch also explains why the original Flash Player isn't likely to be opened soon, thanks to codices and restrictions incorporated therein. That is certainly disappointing, but it may be that what is done is done in this case. It certainly seems that Adobe is willing to look ahead, and embrace the benefits -- and competition -- that opening their products will undoubtedly bring.



Jesse Babson uses OStatic to support Open Source, ask and answer questions and stay informed. What about you?



2 Comments
 

Why not ask Adobe if they are going to remove the restriction (in their Flash PLayer license) that anyone who has ever installed the Flash Player cannot work on development of open source alternatives such as Gnash. This is the biggest single change they could make to be more open source friendly.

0 Votes

Hi there,


I can't find what provision or statement in the Flash Player EULA you might be referring to with this declarative. It would be nice to have more than a "blanket condemnation" as you stated here.


So what part of the EULA are you referring to?


davemc


0 Votes
Share Your Comments

If you are a member, to have your comment attributed to you. If you are not yet a member, Join OStatic and help the Open Source community by sharing your thoughts, answering user questions and providing reviews and alternatives for projects.