RE: [flexcoders] Re: Question to Adobe about Flex Framework 1.5 Code Quality

Fri, 14 Apr 2006 10:13:37 -0700

Yeah, Adobe is so terribly unresponsive.  Its too bad that their engineers don't actually take time to respond on random forums or anything.  Why won't they just put out a new version that directly addresses the community's reaction to the 1.0 product?  Hmm...
 
Thank you, drive through.
 
-rg
 

From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Mykola Paliyenko
Sent: Friday, April 14, 2006 6:25 AM
To: [email protected]
Subject: Re: [flexcoders] Re: Question to Adobe about Flex Framework 1.5 Code Quality

Ok,
as a result we have a FlexCompiler servlet that has a memory leaks and kills application server periodically. It is absolutely a stop-ship bug but Adobe has not released new version of Flex 1.5 yet. As a result there is no stable version of Flex. Yeah I'm realizing that Flex is pretty far from being open source, I just cannot imagine how people can sell such poor product for the great price.

About breaking code. It is absolutely not acceptable having releases once per year or even more like Flex does. Maybe I'm just from another world but I think being not open to the community like Adobe do is a way to produce the poor quality. Flex has great idea but no good expertise from the community. All the critics about Cairngorn, FlexUnit is just ignored however it is obvious that Flex need to have a strong community involved in development of the components and the architecture

Look at Java community, great success stories of Spring, Jboss, Apache and tones of the other really HQ products. We get addicted to the good quality of the design, Not the 200+ UI classes extended from the IEventDispatcher.

WBR, Mykola

On 4/13/06, Weyert de Boer <[EMAIL PROTECTED]> wrote:
Mykola Paliyenko wrote:
>
>     I don't think you should change working code only because it's
>     doesn't
>     have the perfect design, but that might just me. Of course, you
>     can do
>     something refactoring. You can only break ;-)
>
>
> LOL,
> With such approach Flex will remain the same crap as it is no
Well, I am not rewriting working code within a current release cycle. Of
course, you can branch off a version of the code you gonna clean up, for
version X.Y.Z. But I am not someone who will update framework code of a
current version/release only because the code quality sucks. You can
change such issues step-by-step without breaking current functionality.
I should change the design of one of my components, I can tell you my
clients wouldn't appreciate it, neither that you probably like breaking
code because a partner changed the design of the code.

YAHOO! GROUPS LINKS





--
WBR, Mykola

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com


YAHOO! GROUPS LINKS



Reply via email to