flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christophe Herreman <christophe.herre...@gmail.com>
Subject Re: Painful story...
Date Fri, 15 Jun 2012 16:26:19 GMT
I agree that we should not silence people that want to discuss HTML vs Flex
as we can only benefit from these discussions. However, this is the
flex-dev list, intended for people who are actively working on the Flex SDK
code. I would encourage everyone to check the flex-users list for
discussions like the current one so the the focus of this list can stay on
the SDK itself.



2012/6/15 Doug McCune <doug@dougmccune.com>

> >
> > 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.

Christophe Herreman

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message