Ted Patrick - Demos & MAX @ Adobe Systems
Note: This is the personal blog of Ted Patrick. The opinions and statements voiced here are my own.
The Adobe walled garden of knowledge
DIGG IT!
8
Comments
Published
Thursday, May 29, 2008
at
5:58 AM
.
As an ecosystem we do not share knowledge very well and over time this has essentially created a very large walled garden. If you are in-the-know regarding the ecosystem or sub-segment of it, you can see all the value clearly and know where and how to get what you need to succeed. If you are outside the wall (new to Adobe tools and technologies), you see a very large intimidating wall that looks proprietary at first glance.
I don't think anyone in Adobe had a vision of building a large wall that looks proprietary but alas here is this wall and behind it is an ocean of knowledge on how to make great experiences. Actually we have spent a great deal of effort to tear down the wall around our runtimes and core technologies with Adobe Labs, Open Source Flex, Blaze DS, Bugs.adobe.com, Open Screen Project, and Tamarin but we still have a vast quantity of knowledge in the community that is not shared.
I believe that the root cause is actually that a majority of our output is compiled and thus the source code and context remains hidden from view. View Source in the browser really enabled anyone to learn HTML/JS and this "forced sharing" makes it feel much more open. SWF on the contrary is a dark magic and how it works and how to make it do amazing things is not shared automatically. It SEEMS closed and proprietary because the source code is not present and thus the knowledge and context behind great projects are by default locked into a vault. On one hand it is really great that these formats are compiled but on the other we must do extra work to share knowledge. I believe that the "lack of sharing" is the subtle gravity that is holding back our ecosystem and that if Adobe made it easier to share knowledge we would move dramatically forward, actually violently forward.
There are some large projects underway at Adobe, "ION" and "Hyperdrive", to tear down these walls and force knowledge into the open. I am looking forward to working on them with you and helping the community share knowledge more openly, more easily. I also want to make sure that anyone sharing knowledge gets full credit for their contribution and that value flows towards those that share in the community.
Back to tearing down this wall...
Details coming soon!
Ted :)
8 Responses to “The Adobe walled garden of knowledge”
Post a CommentWhere to find me:
Ted on Twitter - @AdobeTed
Ted on Adobe Groups
Ted on LinkedIn
Ted on Facebook
Ted at Adobe
Latest
- Changing roles within Adobe
- Dell.com on Flex 3
- FlexJobs hits 1000 subscribers
- ILOG Elixir - OEM Licensing Changes!!!
- Google Maps Flash API - Distributed components/ser...
- No news is good news!
- 8.1 Megapixel Camera for $160
- Next Dreamweaver - A killer app for HTML/JS/AJAX
- Verizon on Flex 3
- Flex 4 - Enhanced States
Lists
Links
Jobs
Flex JobsArchives
- May 2003
- June 2003
- July 2003
- August 2003
- September 2003
- October 2003
- November 2003
- December 2003
- January 2004
- February 2004
- March 2004
- April 2004
- May 2004
- June 2004
- July 2004
- August 2004
- September 2004
- October 2004
- November 2004
- December 2004
- January 2005
- February 2005
- March 2005
- April 2005
- May 2005
- June 2005
- July 2005
- August 2005
- September 2005
- October 2005
- November 2005
- December 2005
- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
- October 2006
- November 2006
- December 2006
- January 2007
- February 2007
- March 2007
- April 2007
- May 2007
- June 2007
- July 2007
- August 2007
- September 2007
- October 2007
- November 2007
- December 2007
- January 2008
- February 2008
- March 2008
- April 2008
- May 2008
- June 2008
- July 2008
- August 2008
- September 2008
- October 2008
- November 2008
- December 2008
- January 2009
- February 2009
- March 2009
- April 2009
- May 2009
- June 2009
- July 2009
- August 2009
- September 2009
- October 2009
- November 2009
I don't think the 'View Source' thing has a big part of responsability here. Look at Java, applications have always been delivered as bytecode-thus-hidden...
In fact Java seems open-source because there are plenty of big projects that are open-source... So somehow the open-sourceness of the company comes from the ecosystem around it. So in my opinion your latest moves (gumbo, blazeds, swf, openscreen) go in the right direction.
'You are on the right track Adobe' :)
Interesting project names ("ION" and "Hyperdrive"). Gets the imagination spinning...
This sounds like a good direction to take, so good luck!
HA! Thanks for the profound post, Ted. I'm sure I speak on behalf of the Adobe community that we are anxiously awaiting to see what you all have up your sleeve.
Something like a mix between SVG and Flash would be a good choice too. Not compressed SVG, only an easy way to create code directly from HTML. Of course not to create weighted application like Flex ones. Just to create graphics and animations when Flash is a better choice than Javascript. It could favor Flash adoption instead of Javascript in many cases and help to learn how to use Flash player.
With this pseudocode, the mandatory option is to have a report of a public API exposed by the animation that could be exploited from HTML without to have to expose the complete source. Like exposed API of ActiveX, DLL, etc... This allows reuse of the application without opensourcing it. It is a good choice for many corporate project (not all of course).
On the long term (standardization adoption by search engines), this solution offers a way to expose meta tags, or deeper method to reference the content of the animation.
tek,
I am not sure the problem is technical in nature. I would love to see a human readable SWF format but that still would not promote sharing. Great points though!
Ted :)
Anatole,
Amen to the Culinary University, violent agreement here!
Ted :)
The fact that Adobe started paying (some...) speakers at Max is already good step forward.
On the other hand: .NET also took years to become popular and their Visual Studio is way more expensive. Looking at the fact the Deloitte is looking for Flex developers in every state of the US as part of its 'emerging technologies' department is a very good sign (but clearly shows that RIA is currently 'just' an emerging technology).
One thing that could help a lot is getting more companies to build (affordable) Flex components (with source included). This way you can be confident that you don't end up in a situation where you have to build complex components yourself. Because lets face it: some essential components have been added to Flex 3 but the majority of the components hasn't been enhanced (or is it already possible to have tabs on the left or right of a TabNavigator)...
You must be a real Star Wars fan because the two hyperlinks within this article point to the Star Wars site - http://www.starwars.com/databank/technology/hyperdrive/
Frankly, I am a Star Trek fan so your Hyperdrive is our Warpdrive. However we both get there one way or another.