flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gordon Smith <gosm...@adobe.com>
Subject RE: Can Adobe kill Apache Flex
Date Tue, 21 Feb 2012 20:47:39 GMT
> Adobe ... can change something in the runtime that breaks for example current Flex 4.6

Although I guess that's technically true, I don't see how it would be in Adobe's interest
to break the web by making existing SWFs stop playing, so I don't think it's plausible.

- Gordon Smith, Adobe

-----Original Message-----
From: charles.monteiro@gmail.com [mailto:charles.monteiro@gmail.com] On Behalf Of Charles
Sent: Tuesday, February 21, 2012 12:26 PM
To: flex-dev@incubator.apache.org
Subject: Re: Can Adobe kill Apache Flex

thanks for the input, let me put it another way. Adobe can change the runtime anytime they
want. They have not made the runtime code accessible to the Apache Flex project. Its within
the realm of possibility that they can change something in the runtime that breaks for example
current Flex
4.6 apps. Since you don't have the runtime code accessible how will you go about fixing the

And I have not played with Java for a while. I know there's an open JDK .
Isnt' the Java runtime open sourced as well ?

On Tue, Feb 21, 2012 at 2:55 PM, Michael A. Labriola < labriola@digitalprimates.net>

> **Sorry all, formatting was messed up on that reply, hoping this one 
> is
> better.**
> Hi Charles,
> Answers integrated below:
> >So this is what I mean by the subject line. My understanding is that 
> >the
> Flash and Air runtimes have not been open sourced which poses a 
> vulnerability , so I think , that whatever advancements made to the 
> runtimes by Adobe >will be incompatible with the Apache Flex project's 
> advancements.
> That is not necessarily true. Think of the Flex framework as a Java 
> project like Hibernate or Spring and the Flash Player like the Java 
> Virtual Machine. Oracle controls the Java virtual machine's direction and features.
> When they add new features, any of the existing projects are free to 
> use them. So, while Oracle may not decide to implement a feature 
> simply to aid a Spring use case, it does not preclude Spring from using it.
> >Am I correct ? Adobe is claiming a buffer period of 5 years for 
> >projects
> builit with Flash Builder 4 i.e. Flex SDK 4.6x but after 5 years that 
> code is also subject to be rendered incompatible with the newer runtimes.
> No. Adobe is promising that existing code will run for a minimum of 5 
> years on the existing runtimes with no changes. That does not mean 
> that code will cease to work, etc. Remember, Flash Player today still 
> runs code written in the 90s and before. However, from their 
> perspective, things like the iPhone didn't even exist 5 years ago, so 
> it is difficult to predict what shape the runtime may take in future 
> years... they are providing a minimum just so customers understand 
> they have at least that time without significant risk.
> >There's also the possibility that changes to the Adobe runtimes to
> accommodate for example Windows 8 may render Flex apps dead on Windows 8.
> That is highly unlikely and I am unsure where you are getting that 
> information. There is still ongoing discussion on how things like 
> Flash may be supported on windows 8 as it is still in development. As 
> such, Adobe has not direct control over decisions that Microsoft 
> makes, just like decisions that Apple makes. Further, as you just 
> noted above, they have already said Flex apps will work in the 
> existing runtimes for a minimum of 5 years. The bigger risks in this 
> area are Microsoft 'pulling an apple' in certain areas and deciding 
> Flash Player wouldn't be allowed. However, even in the case of Apple, we have a solution
to deploy there and would anticipate one here.
> >All risks I understand but I guess my over reaching question is what 
> >is
> Apache Flex doing so that Flex will be able to run on the probably 
> forever to be ubiquitous upcoming Adobe runtimes.
> Going back to my Java metaphor. We, right now, are deploying only on 
> Adobe runtimes. This means all of our development and all of our 
> testing is on these runtimes. In other words, we watch for changes to 
> our virtual machine, we decide which ones we want to use, and we use 
> them where applicable. This is the same process that all of the major 
> java frameworks need to follow.
> Make sense?
> Mike

Charles A. Monteiro
sent from the road

View raw message