"it seems that moving Falcon to a direction where it can target other
runtimes is going to take much less time than a complete rewrite of the
framework"
Not sure at all. its hard to say, and maybe Gordon could try to answer.
Check my other thread: its not only a new target / new language issue here!
If we want to get better performances, the framework has to be re
architectured, and it seems (still has to be verified) that rewrite from
scratch is more efficient than trying to use the current code base.
Le 16/11/2012 18:46, Nick Tsitlakidis a écrit :
+1 to everything Nicholas Kwiatkowski stated.
AS3 is a matured language and if your objective is to target other runtimes
then you wouldn't convert to AS4 anyway.
I'm not an expert on compilers but it seems that moving Falcon to a
direction where it can target other runtimes is going to take much less
time than a complete rewrite of the framework.
In my opinion, at the moment the amount of commitment here is healthy but
not large enough to have even a basic subset of Flex available soon if we
rewrite the framework (whether it is haxe or AS4 or AS3 or whatever else)
Planning for the future is key here but removing everything and starting
again is not the right choice. We can plan for the future by looking more
realistically on what targets we want for Flex. Then we can start spending
time on creating a me lightweight architecture for the existing code and
making sure that Falcon starts supporting the targets we want.
On Fri, Nov 16, 2012 at 7:33 PM, Alain Ekambi <jazzmatad...@gmail.com>wrote:
Hello folks,
I would like to add my 2 cents to this interesing discussion.
First let me share my experience with the Flash platform.
We have been building Flash based solutions for many years now.
We have different set of products mostly based on GWT that cover all the
spectrum (Native mobile, HTML5 mobile, HTML5 Desktop, Flex, AIR ).
And i can tell you that our Flash based products are by faar the most
succesfull !
Hard to believe no ?
A couple of weeks we had a beta release for the version 3 of our GWT
binding for Flash (http://emitrom.com/flash4j-beta).
Download numbers were just insane ! Breaking every records we ever had for
a products.
And that after all all the bad moves done by Adobe.
For what I can say 99% of our customers (And we have some big ones) use
our Flash products because it runs on the Flash player!
Not because it could compile down the JS.
With all the respect there are simply way better JS based libraries.
If i want to target HTML5/JS/CSS today(and tomorrow) i def wont be thinking
about Flex/MXML/AS3.
The same apply for our customers.
Some of you are talking about Flex/AIR on mobile and think that an HTML5
output will make things better.
Let s keep it honest. Flex is simply a non factor on mobile and will never
be a major player.
No matter how we turn it.
And compiling to HTML5 wont change that. There are simply better
alternative on the market.
I ve said it many times on this forum.
All this talk about going HTML5 with Flex is nice and surelly interesting
from a technical point.
But brings nothing to most customers.
Our focus should be on making Flex even better for Desktop RIA (I do have
some plans with FaBridge that i hope i will be able to commnunicate soon).
The rest is simply waste of energy and time.
Cheers
2012/11/16 Carlos Rovira <carlos.rov...@codeoscopic.com>
Hi Justin,
as someone with lots of apps and products written in current Flex, I
would
want to continue with my products migration to new versions. But the
reality out there is that all ways points to a new rewrite. I'm sure
there
are people here that wants maintain and evolutione the actual framework,
great!
I, as others prefer a new child, so I would spend my time in that kind of
effort.
btw, I see that mostly my apps and products will end if Flex 4.x, but
maybe
some day could be migrated to the new Flex 5.x . All depends on how good
that new framework came and if gets the necesary traction to mimic the
actual Flex 4.x. Only time will tell, in the mean while, I'll try to
upgrade to new Apache Flex official releases to stay up to the latest
versions...
2012/11/16 Justin Mclean <jus...@classsoftware.com>
Hi,
a new flex 5 from scratch concept would not be trying to be
compatible
backwards.
So it's not Flex then but a new framework. I'm sure that would be fun,
but
how would that serve the current users of the Flex framework? Would
there
be a clear migration path?
If the task of write a new Flex is huge...
So let don't and try and improved the one we do have, it's sounds a lot
easier to do and more useful to me.
Just my opinion, and you're free to do what you want on an Apache
project,
so don't let me stop you :-)
Justin
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F: +34 912 35 57 77
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es
