On 11/16/12 6:23 PM, "jude" <flexcapaci...@gmail.com> wrote:
> That is my point in staying with what we have. The Flex SDK has had some
> constraints on it that made it what it is today. I'm not against starting a
> new or full rewrite but I would say let's get this project going on the
> current code base first. Let's make it easy for long term contributors to
> contribute and soon after support drive by contributors. When the dust has
> settled then we create a branch or two to test performance improvements
> out.
I have tried my best to get our committers to commit code on the current
code base, but so far, I have not seen nearly as much activity as I would
have expected or hoped, and the reasons I hear have to do with being too
busy just trying to survive and the interwoven nature of the code making it
scary to start making changes, even with mustella as a validation suite.
> What we don't know right now (maybe you do) is where the bottlenecks
> are in general (code or rendering) and more importantly where the
> bottlenecks are in our applications and then how and where to optimize. I
> wish there was a performance monitoring tool that would show us that
> information but none exist.
I have yet to see rendering be an issue on the desktop. I have heard it is
an issue on mobile devices, but haven't profiled any myself, but basically,
if you are running a lot of unneeded code, you are putting even more
pressure on the renderer to be fast.
>
> It'd be 1000x better for
> developers if Adobe would say Flex can run fine on Flash going into the
> next ten years instead of saying Flash is for gaming.
Where and how should Adobe present this message? I'm not promising that
they will, but I want to understand who it is targeted to.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
