I do not use AMF for enterprise level applications. AMF falls short of our
requirements. But the bottom line for us for converting to FlexJS would be
seamless operation(look / feel / interaction) in all major browsers (excluding
IE) and the ability to compile it using our existing spark based projects
without having to having to create hundreds of JS beads / customizations.
Understandably heavier, but compatibility is more important.
The only selling point to me for converting to FlexJS would be that I could
cross compile Adobe Air apps and FlexJS. If not, then it would be creating
everything from scratch again. If that's the case I would have to consider
all the available SDK's out there before making a decision.
-Mark
-----Original Message-----
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Friday, January 13, 2017 1:11 PM
To: dev@flex.apache.org
Subject: [Non-DoD Source] Re: [FlexJS] Some things still missing ni FlexJS
On 1/13/17, 12:44 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Well from my point of view it was the whole “write once run everywhere”
>thing.
>I was totally annoyed of having to write UI things once and then patch
>and bugfix things for all the other Browsers.
I would say that fits under the "Developer Productivity" umbrella.
>
>But in general I think you (Alex) and I have one great difference in our
>assumption of who will probably be our generation 1 users.
>
>You assume it’s mainly the people wanting to create new applications.
>That’s why you see 1.0 the way you do it.
That is an incorrect assumption.
IMO, there are at least some existing Flex apps that don't use AMF. Now
it may turn out that we will have AMF shortly, but until it is done, those
who don't need it can start migrating their apps today. Some folks are
already migrating. I will believe that AMF is used by the vast majority
of Flex apps, but as I said upthread, we simply need to attract more
committers/contributors to really get FlexJS off the ground. Some folks
believe that declaring something as 1.0 will invite more folks to try it
and thus get involved. I don't have a strong opinion, but that sounds
like a reasonable approach, and better than telling folks not to try
FlexJS for another year or two and wait for the few of us who are active
committers to reproduce all of these killer features that a much larger
team of full-timers did at Adobe over many more years.
Flex 4 had many more features than Flex 3, which had more features than
Flex 2 which had more features than Flex 1.0. FlexJS 1.0 may only allow a
small percentage of Flex customers to migrate, but again, if that brings
in new contributors we can handle more Flex customers with FlexJS 2.0 and
so on.
There may also be a way to get traction with new customers and new apps as
well by trying to get attention from Cordova developers, CreateJS
developers, etc. I don't care who gets to production first, whether it is
a new app or migrated app, but mainly, I think a testimonial is what we
really need since we don't have a budget for marketing. So when folks
show up with a need in order to get to production, I will try to help them
out.
-Alex
