Here's the thing. Since Adobe donated Flex to the Apache Project, I've made a lot of money on the excellent work of many of my colleagues here at Apache. I've made enough to pay my mortgage, utilities, buy a new car and be very comfortable. Sure, the number of web projects involving Flex is on a downward trend, but for every web project I'm not doing in Flex, I've picked up two mobile projects.
Will this train last forever? Nothing lasts forever. But despite my dependance on Adobe AIR, they've been keeping it up -- to the point where they've released 5 major versions in the last two years. It's a bit more than maintenance mode -- they've been not only fixing bugs but also adding new features. Even if Adobe stopped making AIR for mobile, because of the way it compiles (into native apps), I have a runway of at least 18 months before I need to adopt a new solution because I can still use the same compiler to produce new apps. Yes, they've let their IDE languish, but I've found home in JetBrains' IntelliJ IDEA -- from a group that actually pays attention to their customers and have been making improvements as the Flex community has been asking for them. The direction of Apache Flex is purely set by those that want to contribute. If you are interested in moving a particular feature forward all you have to do is write code and submit it. The areas that have passion are the ones that move forward. That is why we are seeing a lot of work on FlexJS -- because people want to see that move forward and they are moving it forward with their own contributions. -Nick On Tue, Dec 9, 2014 at 5:56 PM, Jesse Nicholson <[email protected]> wrote: > > Hmm, well. This effort is dead. Oh oops, sorry, it's very much alive, if by > alive you mean maintaining the software to keep adobe's clients happy. Take > care guys. > >
