flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Malejko <a...@malejko.com>
Subject Re: [FLEXJS][Marketing] why should a web dev choose FlexJS?
Date Fri, 15 Sep 2017 19:22:58 GMT
More strengths to add:
- AMF support getting better
- RemoteObject support!
- Less to re-write when porting Flex apps
- Can use other JS components (with caveats, unfortunately)
- Type-checking, SWF output and validation
- Works in several IDE's

A few weaknesses to add:
- It's not done yet. The components we use from Flex are not all done in
FlexJS yet.
- No commercial support if you want it (but the Apache support is
wonderful!)
- Lack of documentation
- Smaller community than some of the bigger JS frameworks

I like the Opportunities listed, and the Threats I agree with.

Yes, we could volunteer to contribute; or we could switch to React,
Angular, ExtJS, or something else.. we're on the fence and looking in to
all of our options, of which there are many these days.



On Thu, Sep 14, 2017 at 10:46 PM, Berty Tonta (Leadstalk) <
berty.tonta@leadstalk.pro> wrote:

> If it has not been done yet, and from a marketing perspective, would a SWOT
> help?
>
> The point of the SWOT (example below) would be to look at the reality and
> then identify those engaging arguments to (1) answer weaknesses and threats
> and (2) leverage on Strength and opportunities.
>
> We could then select the 3 - 4 key arguments that really makes FlexJS stand
> out.
>
> STRENGTH
>
>    - Robust AS3 foundations
>    - Multiplatform
>    - Open Source
>    - Security???? (I'm not a developer and need you to confirm)
>    - ...
>
>
> WEAKNESSES
>
>    - Association with Flash
>    - Abandoned by Adobe???
>    -
>
>
> OPPORTUNITIES
>
>    - AS3/Flex a more robust/structured development platform
>    - A potential enterprise class solution
>    - Rebirth into an open source platform
>    - Powered by the community
>
> THREATS
>
>    - Other "native" JS platforms
>    - Potential to be rejected by pure JS/HTML5 developers
>    - Perception of poor security....Flash legacy
>
>
>
>
>
> Berty Tonta
>
> ____________________________________________________________
> ________________
>
>
>
> LEADSTALK - 4 BENGALI STREET, BEAU BASSIN, MAURITIUS
> TEL  +230 57 43 81 34 - BERTY.TONTA@LEADSTALK.PRO - LEADSTALK.PRO
>
> On Thu, Sep 14, 2017 at 11:38 PM, gkk gb <modjklist@comcast.net> wrote:
>
> > In addition to...
> >
> >
> > "Why should a web dev choose FlexJS to write JS applications, and not go
> > with a more mainstream option like e.g. TypeScript/Angular?"
> >
> >
> > it may also be useful to think of the end customer. That is,
> >
> >
> > "Why should a company prefer their app to be written in FlexJS rather
> than
> > ..."
> >
> >
> > The company will need to support their app throughout its lifecycle by
> > hiring developers, etc, which, the further you go from mainstream
> > technologies, is harder to justify. There should be some compelling
> > business reason(s) to do so (faster development, etc.).
> >
> >
> >
> > >
> > >     On September 14, 2017 at 6:38 AM Piotr Zarzycki <
> > piotrzarzycki21@gmail.com> wrote:
> > >
> > >     Hi All,
> > >
> > >     Erik on dev [1] list came up wit interesting question. I'm posting
> > it also
> > >     here:
> > >
> > >     With the upcoming fork and renewed focus and most likely some
> > publicity, I
> > >     want to ask the community to answer this question:
> > >
> > >     Why should a web dev choose FlexJS to write JS applications, and
> not
> > go
> > >     with a more mainstream option like e.g. TypeScript/Angular?
> > >
> > >     I think that if we can answer that question in a compelling way, we
> > are in
> > >     a good place as a project (from a code perspective, at least) and
> it
> > gives
> > >     the marketing folks something to work with.
> > >
> > >     [1]
> > >     http://apache-flex-development.2333347.n4.nabble.
> > com/FLEXJS-Marketing-why-should-a-web-dev-choose-FlexJS-td64292.html
> > >
> > >     Thanks,
> > >     Piotr
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message