flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From f...@dfguy.us
Subject Re: "The Player", a case for an independent Flash Player
Date Mon, 23 Feb 2015 19:37:07 GMT
I really think Stephane makes some great points. It's a good idea though to keep things constructive
and on topic in regards to Flex too as Erik mentioned.

While work on a different player seems to have been something actively tried a few times,
what I've been pondering is possibly trying to cross compile one of the browser sources to
as3. That way we could leverage all of the good things about the web standards within a flex
or air app. Some of the built in HTML views have a lot of limitations so this might allow
for reusing a lit of the existing code out there, or combining project assets into a single
codebase.

I've done some initial work on it but don't have anything completed as of yet.

David



-----Original Message-----
From: Stephane Beladaci <adobeflexengineer@gmail.com>
To: dev <dev@flex.apache.org>
Sent: Mon, 23 Feb 2015 1:24 PM
Subject: Re: "The Player", a case for an independent Flash Player

I understand the possible distraction from the objective of the
mailing list, however it is concentrated on a single message thread
that anyone can easily ignore. It is also important to identify the
concerns and criticism from the community in order to define the right
path for an alternative player in an attempt to bridge the gap between
what Adobe seems incapable of accomplishing, what the browser war
render nearly impossible to accomplish, what the Jobs' Apple tries to
kill, and what the new Apple makes possible.

You simply cannot consider the work, and future of Flex developers
without to have a holistic approach, analysis and understanding of the
business, corporate and technological of the developer communities,
browsers landscape, and app marketplaces.

On Mon, Feb 23, 2015 at 7:13 PM, Erik de Bruin <erik@ixsoftware.nl> wrote:
> This discussion was intended to start the development of a Flash
> Player alternative, and as such got a preliminary pass on being OT for
> this list.
>
> I think it has ended up being just a "bash the Player, Adobe, Apple
> and all let's include all browser vendors for good measure" thread, so
> I, again, respectfully ask that it is continued on another forum.
>
> This list is the dev list for the Apache Flex project, all discussion
> on it should at least be tangentially related to that topic.
>
> Thanks,
>
> EdB
>
>
> On Mon, Feb 23, 2015 at 7:32 PM, Stephane Beladaci
> <adobeflexengineer@gmail.com> wrote:
>> The "proprietary" tiny bit of the player, which is a fraction of the
>> whole Flash ecosystem mostly open source, is precisely what made it a
>> success and what made JS a failure. JS implementation is left to the
>> browser, and you can be sure they will use that last word to screw
>> each other, block each other, and make sure the browser never compete
>> with their app store. We have seen it over and over, bugs marked by
>> Apple "no to be fixed" by executive order to refrain Facebook from
>> building its HTML5 game platform codename "spartan"; H264 yanked by
>> Google to block Apple and MS. Safari on iOS 7 called by HTML5 expert
>> "the buggiest mobile Safari ever".
>>
>> Meanwhile Adobe keep adding features and move forward with no block,
>> no endless discussions and no matter the constant complaining from the
>> developers community never happy with what we got, the player and AIR
>> are still half to full decade ahead of any <whatever>.JS technology
>> with decent browser penetration.
>>
>> It is because of the proprietary piece of the Flash player that the
>> same hypocrite browser vendors cannot mess with it, and Apple had to
>> ban it entirely to avoid having the Flash Platform take over its
>> AppStore with Flash 9, AS3, Flex and AIR. Good news is, that ban
>> exposed Apple much more than merely messing with JS implementation,
>> and I believe there is an antitrust class action lawsuit that can be
>> pushed by the Flash developer community. If I successfully lead this
>> to court, the discovery process might expose the whole nasty Silicon
>> Valley browser war.
>>
>> As far as security is concerned, my guess is that it is all a question
>> of popularity, when every page on the web will contain HTML5 ads with
>> JS pushed to the limit as replacement for Flash, you will see JS
>> security risk rise to the sky. It already started, most security
>> reports warn of the HTML5 security risk.
>>
>> On Tue, Feb 17, 2015 at 3:49 PM,  <flex@dfguy.us> wrote:
>>> That's probably true but what I'm wondering though is does this actually help
right? So if Mozilla is then maintaining the code then it's dependent on them to fix any security
flaws in terms of their own release cycle for fixes. Plus the ability of the implementation
is again dependent on whatever capabilities exist in the browser as the runtime like you mentioned.
>>>
>>> So what is occurring to me is that most likely media like that outlet just don't
like the idea of a "proprietary" runtime that's supported and maintained by a company in general,
so it's sort of cool to promote an implementation by another company that's not deemed to
be as proprietary like Mozilla. It's sort of an ideological argument I think that's really
at the root of all this stuff. I think there have been a bunch of swf players out there for
years right? But if this could allow all of that content to be played on iPads or etc then
I'm sure it would help out.
>>>
>>> No one seems to care about all the other proprietary runtimes out there, or Apple's
closed environment, or Android or anything else being closed in varying forms, or that whole
Mozilla DRM plugin or etc.
>>>
>>> David
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Tom Chiverton <tc@extravision.com>
>>> To: dev@flex.apache.org
>>> Sent: Tue, 17 Feb 2015 9:23 AM
>>> Subject: Re: "The Player", a case for an independent Flash Player
>>>
>>> I think The Register's angle is the Adobe implementation of the Flash
>>> runtime is bad and full of security issues.
>>>
>>> In theory Shumay runs in the JavaScript sandbox, so inherits all the
>>> protections and 'many eyes' of previous work on securing it.
>>> When was the last time there was a off-by-one arbitrary code execution
>>> issue in a major JavaScript implementation ?
>>>
>>> Tom
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message