Warning: I can't decide if I'm just playing devil's advocate or am truly concerned about this, but below are some worst-case scenarios, which may need to be taken with a grain of salt.
My latest proposal is that we rename packages from "flash.* to "webgl.*" and teach the compiler how to map things. And maybe also update the reflection library to be aware that there was a mapping. We might end up having the compiler do this sort of thing to migrate Flex code bases as well. Yes, it may mean that migration isn't automatic. But IMO, until we find a clean way to do weak references in JS, there is going to have to be some migration pain. On 4/18/16, 6:47 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: > >We already have package names like jquery.*.* and createjs.*.* where we >are >using the same package names for consistency. Are we proposing to change >all those package names as well, so that we dont set expectations of doing >everything that jquery does? The jquery and createjs implementations actually use Jquery and CreateJS on the JS side, so it should meet expectations. There is a potential outcome where we end up having more demand for Flash emulation in JS than Flex. Or spending more time on Starling than on Flex. If that's where the community wants to go, I can't stop it, but this project is called Flex. And, IMO, the big money is in enterprise code bases in Flex. > >If it turns out that that lot of folks complain about the classes not >meeting the expectations, we could probably add the features or worst case >swap the package names to flex.* We can change the package names and have the compiler do-the-right thing. If we set the precedence of using "flash" it will be harder to change in the future. We'll get backwards compatibility complaints and the search engines will turn up "flash" stuff for a long time. When I think about the person-hours devoted to Flash at Adobe, it is hard to imagine this community finding the time to even do a fraction of that investment. It seemed like even Google was having trouble making Pepper Flash a true equivalent. And there might be increased legal issues due to things like this [1]. -Alex [1] http://blog.smartbear.com/apis/api-copyright-and-why-you-should-care/
