You are welcome to your option/opinion, but the few folks I've talked to make me think differently.
Some folks haven't moved from Flex to JS and if they decide to move someday will be a lot of work and if FlexJS is less work, we become a viable choice. It is important to set expectations. If we make folks expect a 1:1 drop-in, we will likely disappoint, at least in early builds. And then there's folks who might be interested in making new apps that truly run everywhere. All of those other JS frameworks had 0 users at one point in time. And like I said, nobody at Adobe said I couldn't try, and I've got all day to try :-) -Alex On 3/25/14 3:13 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >> Maybe I am too idealistic, but I think if FlexJS does become the most >> efficient way to make money selling RIAs and mobile apps, some of those >> folks will come back. > >My option on this is this: > >Unless it's a drop in 1 for 1 replacement I don't think the take up is >going to be huge. People with existing Flex browser apps who were >considering converting to JS have already done that by now and have >selected a different framework/technology stack, and those who haven't >converted aren't going to want to spend the time/money on learning a new >frameworks and rewriting all of their UI code. > >While the appeal of still using AS and being able to reuse say 80% of >your code the down side is that the UI stuff is hard and tricky to get >right and takes the most time. > >They may also see (correctly or not) a 1.0 release of a framework a bit >risky compared to more mature frameworks out there. > >Then there's the often narrow minded hiring practices around frameworks >in which they ask for 5+ year experiences with framework x rather than >ability to learn and solid experience with other frameworks/AS/JS. > >All of the above matches with my recent experience with existing/past/new >clients - but as they say your milage may vary. > >> We should certainly make our current customers happy. > >The number one responsibility of any Apache project is to it's users. >Just about every project guidelines (including ours) has words to the >effect of "The most important participants in the project are people who >use our software." > >Thanks, >Justin >
