And we might learn things that help us develop Apache Flex to be even better.
On Fri, Jun 15, 2012 at 9:30 AM, Rick Winscot <rick.wins...@gmail.com>wrote: > Doug's comments are well said... discussing the pain-points in a competing > technology is a healthy exercise. > > On Friday, June 15, 2012 at 12:12 PM, Doug McCune wrote: > > > > > > > Your experiences / pains on building HTML apps has no place here. Nor > > > does a debate on the merits of HTML/JavaScript Frameworks. > > > > > > > > > > > I've said it before and I'll repeat it again. This is so very not true. > As > > a community, as a project, as a technology, Flex absolutely is fighting > > tooth and nail against the migration of developers to an HTML/JS stack. A > > proper understanding of the difficulties of layout in HTML is relevant > for > > multiple reasons, including: > > > > 1) understanding how the simplicity of Flex layouts compare to HTML (or > > other stacks) is important when Flex developers debate the merits of > > various options. The Apache Flex community needs to be concerned not only > > with the technical aspects of Apache Flex, but also with the marketing > side > > of things to give developers the ammunition needed to sell Flex as the > > right choice for a project. > > > > 2) since there is an interest in this community in converting MXML/AS > into > > HTML/JS, the implications of how difficult mimicking Flex layouts in HTML > > is an important topic > > > > Now, I agree that the community should be fairly laser-focused *right > now* > > on shipping an initial release. But that doesn't mean we should tell > people > > to not discuss HTML-related topics. They are relevant and they are > > important to the future of this project. > > > > > > >
