Monthly Archives: May 2008

Mozilla World Record Problems

Mozilla is attempting to set a world record for downloading FireFox, good luck with that! The problem I see is that Adobe Flash Player has seen installation spikes daily that go into the 14 Million to 25 Million per day range. We report averages on all our player stats but never the spikes in traffic. It makes me think that we should be much more open about our download statistics regarding Flash Player.

Maybe we should just just submit Adobe Flash Player installs for the World Record and resubmit it as spikes occur.

Although even this gets sticky. If they count Mozilla FireFox 3 downloads according to file size, each download is 12MB average (MAC/WIN/LIN) where Flash Player is far smaller. It gets even worse when you think about auto-update a download, I am sure the OS teams at Microsoft Update see lots of issues.

Too fun!


The Adobe walled garden of knowledge

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,, 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!


Changing roles within Adobe

On May 1 I passed my 2 year mark at Adobe and I took some time off to think very deeply about what I wanted to focus on moving forward. The thing is that I am very passionate about helping developers succeed and have found myself selecting projects related to training (Yahoo & Google) and events (Adobe MAX, Adobe Engage, 360Flex, Etc). Effective this week I will be migrating from Technical Evangelist to focus on scaling Adobe’s events and training in the Platform Business Unit. The change is a great opportunity for me personally and I really believe that we can grow the developer ecosystem/market dramatically with some key changes to our event and training strategy.

The thing is that I will never stop evangelizing; I was passionate before I joined Adobe and I remain so as I change roles within. I will keep on blogging too and with all this “Thermo” and Flex 4 stuff coming I have an endless supply of material to cover.

Now go register for MAX 2008!

More to come!


ILOG Elixir – OEM Licensing Changes!!!

Since posting on Elixir Flex Components, the ILOG team has gotten a steady stream of feedback on OEM licensing. Today ILOG removed the OEM restrictions for small business and start-ups.

I have really been impressed with the quality of these 3rd party components and seeing as the only negative feedback was the OEM licensing restrictions for smaller firms, this change is a welcome addition. I keep seeing these components pop-up in applications and I am sure they will get more use with this licensing change.

Licensing FAQ