Good point on React’s JSX. I did not know that Josh created that site. Cool! I’d love to see some more stuff there! (I just pledged a few bucks as a patron there.)
I think that sources outside the Apache website is probably the best way to get traction (and if someone can make a few bucks off their content, even better). I think we should feature Josh’s site on the Flex site (as well as anyone else who wants to put in the effort of creating learning materials and tools around FlexJS). Harbs On Nov 29, 2015, at 10:39 AM, OmPrakash Muppirala <bigosma...@gmail.com> wrote: > Agree with all your points! > > Here is one more: FlexJS's MXML is a real alternative for React's JSX, > which looks very similar to MXML [1] > > 1. Good timing, I am currently working on node.js support for FlexJS. The > goal is to make FlexJS installable via a simple "npm install flexjs" > command. I hope to get this out soon. > 2. I think Josh Tynjala has a very good blog post with a hello world > tutorial here [2] > > [1] https://facebook.github.io/react/docs/jsx-in-depth.html > [2] > http://nextgenactionscript.com/tutorials/hello-world-transpile-actionscript-apache-flexjs/ > > Thanks, > Om > > On Sun, Nov 29, 2015 at 12:29 AM, Harbs <harbs.li...@gmail.com> wrote: > >> I was thinking of writing a blog post about FlexJS, and I realized that >> FlexJS can mean different things to different people. >> >> 1. FlexJS (or really FalconJX) can be a competitor for TypeScript. I can >> imagine people using it to write framework agnostic javascript libraries. >> 2. FlexJS is a replacement for Angular/React with components, data binding >> and business logic. >> 3. FlexJS can act as a replacement for a lot of the “helper” js libraries >> like underscore, etc. because there’s lots of helper functions built in. >> (If we take as3commons, we get an ton more of those.) >> 4. FlexJS can act as the “glue” that holds different JS libraries together >> to form an app. >> 5. FlexJS adds a lot of functionality you can not get in other frameworks. >> i.e. E4X (once we finish with that), zip processing (via as3commons), >> “real” components that can simply be dropped in, etc. >> >> To increase adoption of FlexJS, I think we need to market specifically to >> these targets. It would probably be a good idea to figure out how to polish >> our message as well as our delivery. >> >> Here’s some thoughts to get this discussion started: >> >> 1. For FalconJX to compete with TypeScript it needs dead simple >> instructions on how to use. TypeScript does this right.[1] Getting npm >> support really talks to JavaScript developers. Maven is fine as well. Both >> is probably the best approach. >> 2. Again, we need dead simple instructions on getting started with FlexJS. >> The installer app is good, but some step by step instructions on how to >> build some “hello world” apps would go a long way. These need to be on the >> Flex website and not buried in some wiki somewhere. >> >> Thoughts? >> >> [1]http://www.typescriptlang.org/#Download
