Hi,
it sounds quite like a short term vision to me.
yes i agree that flex is still good solution for TODAY running on Adobes
runtimes.
maybe for a few years also but its risky and totally Adobe dependant.
Of course theres better JS fraework for HTML5, because flex don't
support HTML5. Flex is not an alternative, so how could there be better
alternatives on the market?
Before flex was able to create native mobile apps, you or your customers
would have never think of Flex for that.
Now it can do it then it becomes a viable alternative.
So if Flex support an HTML5 output, it will be the same result.
We all agree that in the short term flex would have little value to run
on HTML5 has it is TODAY.
But when tomorrow, with better performances of HTML5, Flex could become
the best RIA framework for HTML5 output. why not?
"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."
What makes you say that?
its not a big player because as soon as it was able to run efficiently
with 4.6 Adobe dropped it with all the mess we know.
thats only pessimism.
"Our focus should be on making Flex even better for Desktop RIA"
But what you do when Desktops are only tablets OS and Adobe runtimes are
not running on it?
And what you do when webApps get more popular than natives apps in 6
years for example and theres still no flash player in mobile browsers?
Le 16/11/2012 18:33, Alain Ekambi a écrit :
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
