Hi Harbs, I honestly don't see how the language can move forward when the goal
of FlexJS is to be able to compile to swf. As long as we are stuck with that
baggage implementing async / await and other parallel processing operations
won't be possible without breaking the swf compatibility and fracturing FlexJS.
That's where the crux of my disagreement with the team is. I don't believe
compiling to swf is important in the long term, and by binding ourselves to
that we are limiting out future drastically. In a few years I don't think an
application developer will be willing to switch framework platform without
async / await, generics, or lamda's. I am excited about FlexJS, but honestly I
hope it's ported over to a better language system like typescript or dart.
The world needs a great rapid application development framework with a
declarative UI language, but the world dosen't need SWF's in the future.
From: Harbs [mailto:harbs.li...@gmail.com]
Sent: Thursday, October 13, 2016 12:51 PM
Subject: Re: [Discuss] What's keeping the others from participating?
There has actually been discussion on improving the language. The suggestions
so far have been very small, but steps nonetheless.
I would like to see improvements to the language and they will likely come, but
I think there are bigger ticket items which need to come first. XML and E4X
we made that happen.
Async and await are probably the most significant items on your list for me
Once things settle down a bit, I'd like to see more features start paralleling
The more people we have working on things, the faster improvements will come...
On Oct 13, 2016, at 9:49 PM, Jason Taylor <ja...@dedoose.com> wrote:
> Additionally I'm losing interest in AS3 as it's support for concurrency,
> generics, lambdas, expression trees, generics, conditional clauses on
> generics, async await, etc are terrible and feels like the language itself
> has no interest in moving forward