flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Taylor <ja...@dedoose.com>
Subject RE: WebAssembly Flash ByPass
Date Mon, 10 Apr 2017 21:24:05 GMT
Gary, do you even have any idea what WebAssembly is? You should check out some articles on
it: https://github.com/WebAssembly/design/blob/master/FAQ.md, https://developer.mozilla.org/en-US/docs/WebAssembly/Concepts

In a nutshell the browser vendors finally realized that HTML+JS will never be efficent enough
to implement complex software/games in browser, and thus WebAssembly was born. It was designed
by the W3C committee that included all the major browser vendors.   

Please do yourself a favor and research your opinion before you spread mis-information.



-----Original Message-----
From: Gary Yang [mailto:flashflexpro@gmail.com] 
Sent: Monday, April 10, 2017 2:21 PM
To: dev@flex.apache.org
Subject: Re: WebAssembly Flash ByPass

1) It takes a long time to make a powerful system like Flash Player stable enough, Google
Map has been using webGL for a long time, improved a lot still crash all the time.
2) Politically, none of the major browser vendors would let anything our of their control
grow bigger anymore, Flash Player is the only exception, it came too early and too important
to the web to be killed.

The only chance to implement high performance application across main stream browsers is still
Flash with stage3D AGAL, time has proved it, I don't the majority get it, when it comes to
tech, this is usually it, most just follow what others say.

Sad haaa? What if spent time in implementing Flex with AGAL from the very beginning? Flash
platform might not be on the hanging edge...


On Mon, Apr 10, 2017 at 5:16 PM, Josh Tynjala <joshtynjala@gmail.com> wrote:

> I don't think you can simply compile LightSpark as-is to WebAssembly. 
> I suspect that its rendering code will need serious modification to be 
> able to draw to HTML Canvas or WebGL instead of whatever native APIs 
> it uses now. This part probably wouldn't be trivial.
>
> - Josh
>
> On Mon, Apr 10, 2017 at 1:52 PM, Jason Taylor <jason@dedoose.com> wrote:
>
> > Why would we be implementing anything? I'm talking about taking
> LightSpark
> > as is (with their 252 open bugs) compiling it to LLVM, using that 
> > input
> for
> > the WebAssembly compiler and compiling the output binary as a 
> > LightSpark WebAssembly drop in flash player.  This has nothing to do 
> > with the
> existing
> > FlexJS work and is merely to allow the existing flash apps to run in
> > browser, cross platform without a plug-in (such as Safari on iOS).   Not
> > quite sure what exactly is so crazy here.  Sorry, FlexJS will never 
> > give
> us
> > the performance we (Dedoose) need, so extending the life cycle of 
> > the
> flash
> > player a couple more years to buy us time for a complete rewrite in 
> > a performant client technology is pretty important to us.
> > ~ JT
> >
> >
> >
> > -----Original Message-----
> > From: Gary Yang [mailto:flashflexpro@gmail.com]
> > Sent: Monday, April 10, 2017 1:46 PM
> > To: dev@flex.apache.org
> > Subject: Re: WebAssembly Flash ByPass
> >
> > No mean to be offensive, implementing everything in WebAssembly 
> > feels
> just
> > like talking about living in Mars, even with HTML/Javascript/CSS
> regardless
> > of performance, after so many years ...
> >
> > On Mon, Apr 10, 2017 at 4:18 PM, piotrz <piotrzarzycki21@gmail.com>
> wrote:
> >
> > > Hi Gary,
> > >
> > > Please be tolerant to Jason's opinion and ideas. Apache Flex is an 
> > > open source project and if Jason would like to bring some idea 
> > > here he is very welcome, same as you.
> > >
> > > Piotr
> > >
> > >
> > >
> > > -----
> > > Apache Flex PMC
> > > piotrzarzycki21@gmail.com
> > > --
> > > View this message in context: http://apache-flex-
> > > development.2333347.n4.nabble.com/FlexJS-feature-chart-work-
> > > status-tp61035p61082.html
> > > Sent from the Apache Flex Development mailing list archive at
> Nabble.com.
> > >
> >
>
Mime
View raw message