I think what would be MUCH more productive is a PR effort to show off
really large, well-done Flex apps in enterprises. Developing really large
apps in Flex is much easier than doing the same in HTML/JS today. Even if
the framework might lend itself to some bad practices, or if we don't have
best practices defined to teach people really good ways of writing large
apps, it's still the case that making a well-designed, really large
enterprise app, and working with a  large team of developers, is a hell of
a lot easier with current-day Flex than HTML/JS. Everything from how you
organize your code, to continuous integration stuff, to IDE support for
large code-bases... hell, just having packages to organize your classes!

Flex's problem is not that it's not a viable option for very large
enterprise apps. It's better than almost anything else (for desktop web
apps of course). That's not to say that there aren't improvements that can
be made here, but with the limited resources that will be devoted to Apache
Flex, I'd hope that instead time would be devoted to areas where Flex fares
worse than competitors (performance on mobile, as just one example).

Just my 2 cents.

Doug

Reply via email to