On 3/17/15, 10:28 PM, "Carlos Rovira" <carlos.rov...@codeoscopic.com> wrote: >I think FlexJS has it own reason to live and could be a great option for >people out there, but it need a muscle and union of mind that we don't >have >today. So it's difficult. It would need real investment of resources and >some top companies pushing it forward. I don't think in Adobe, since it's >not anymore the kind of company it used to be, and nowadays for me does >not >have any interest at all, at least for me.
Yes, finding some money and resources would help, but I think one of the reasons Flex is at Apache is to find out if the “Apache Way” can also produce the same or even better results. As most of you learned, relying on a corporation to create and maintain a project is only good until that corporation changes its mind. A major principle behind Apache projects is to be free of corporate decision making. Adobe can stop paying me to work on Flex, but it can’t stop me from working on Flex. So, as I understand it, the Apache Way would be that the 800 or so folks on this mailing list all try to find even a little bit of time to work on FlexJS. I’ve purposefully set up a programming pattern in FlexJS called beads that tries to encapsulate functionality into small classes so that folks working in their spare time can have a better chance at succeeding quickly than trying to change a 13,000 line class and run all of its tests. If half of the folks on this list each found 30 minutes a month to work on FlexJS by contributing a single unit or feature test, or ASDoc comment, or a small feature, that would result in 200 person-hours per month, which easily exceeds my total monthly output. I’d say we don’t even need union of mind. FlexJS isn’t supposed to have one component set, it is supposed to have many. Folks who want low-level components can provide those, folks who want a more Spark-like API can write those. You can wrap, hopefully, any procedurally-written JS UI toolkit and use that. See the version of FlexJSStore that has a few Jquery components in it. Now for sure, if you start in now, you’re going to have to be patient as there are plenty of rough spots and you may not get a lot done in your 30 minutes, but I will try to prioritize unblocking new contributors, so if you don’t give up and keep finding another 30 minutes in the future, hopefully you will eventually start getting this ball rolling. So, the muscle can be one corporation that can push really hard and then decide to stop pushing, or it can be several people just leaning in. Can you be one of those people? -Alex
