carlosrovira commented on issue #648: Tasks to Reach 1.0 URL: https://github.com/apache/royale-asjs/issues/648#issuecomment-570541053 Hi @aharui, as you, I think more people should come by 2020, but moreover, more people should come *after* browsers cut off flash at the end of 2020. So in 2021 I suppose will see migrations in a hurry, since many people use time will caught them. Anyway, I understand your point of view, but don't think we really must to wait for a concrete successful migration with MXRoyale UI Set. Emulation components are a part of the Royale ecosystem and doesn't represent Royale in its globality. We already have other production Apps with Basic and Jewel (and maybe MDL?). So IMHO, that's not a point that should stop a 1.0, since many of us even doesn't work on that part of the technology (and that's another point that shows that is not a crucial part). So making 1.0 wait for that milestone could be something that happen sooner or later and depending on that can be good or bad for Royale. Currently the migration with emulation sets we depend on, is the one from @alinakazi and @pashminakazi. But couldn't say much more about how their migration goes. Will be ready in 1 month? in 6? in 12? Maybe they could bring more light on this on how metrics they have about it. For me 1.0 is about having a solid tech that people can build without pain and use without find problems at each step they do, or not finding some component they need (I mean core components), and something we can release at least each two months without much pain. MX/Spark, will be desirable, but not should stop us. To end, I think people migrating from Flex will be users, but our real interest should be all other users that use any other tech out there, even React or Angular. Check the actual React users, that's a real big number to try to capture. Our big goal should be to attract React users to Royale. Numbers are pretty significant. I don't want we to fail for people that know and use React. Since that market is the one we should go for. The Flex migration market is small and each day getting smaller with people choosing React over the rest of techs. We are not listed here [1], we need to start appearing in webs like that as a real alternative. Anyway, thinking a bit more in 1.0 needs. I found a couple of more things that would be good to have in 1.0: 1.- Separate MXRPC and other non visual classes from MXRoyale, since these are the things that not doing now will make people to refactor their configs at later time. So I think we should do this before 1.0. 2.- Finish Jewel Themes for plain and dark flavors [1] https://stateofjs.com
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
