On Tue, Jul 10, 2012 at 3:54 AM, Gary McGhee wrote:
> In order to free up the Flex SDK to move forward, I'm thinking it would be
> advantageous to split the SDK into "Flex-Core" and "Flex-More" like Merb (a
> Ruby library that merged with Rails).
This is actually an idea I like. I don't like th
Gary,
Personally, I'm not a big fan of this. I've seen some other languages do
this, but I've also been stuck in "dependency hell", even for seemingly
core components. We also have to play the balance game as far as what is
licensed under the Apache License, and what isn't as well (for example,
In order to free up the Flex SDK to move forward, I'm thinking it would be
advantageous to split the SDK into "Flex-Core" and "Flex-More" like Merb (a
Ruby library that merged with Rails).
This would mean that the compiler, standard libraries and core components could
move forward in versions m
