carlosrovira commented on issue #641: Fix PAYG violations and code debt URL: https://github.com/apache/royale-asjs/issues/641#issuecomment-569668001 Hi, Thinks like Reflection, Metadata, Crux are the things I expect users will want for real apps. So for this ones I think Greg is right in have it by default since are the features a normal royale user will want in a framework like this (if not probably will go with simple solutions). So For Reflection, people that will not want it should have a way to remove it completely. I think that kind of "switch" should be easily implemented, and will be an optimization technique for people for worried about it. Modules are other important feature for any serious App (not short, tiny examples or Hello worlds), so as well should be a first citizen feature and again be optimized via some switch for people that does not use it. I think all of this are very important things, but my opinion is that we still have some issues more important to solve for 1.0 that I'll put on priority. And I'm talking of things people will want to use and right now they can't.For example: - CSS issues: We still have many issues to solve in CSS handling, to name a few: selectors like nth-chilld(even), [attribute~=value] or :not() and many other css keywords like @keyframes are still not usable in Royale and compilation breaks when we try to add this. - Bindings: One of the biggest frustration things for newcomers to Royale are bugs with bindings. We are here freely, and we all can spend our time in whatever we want. All work that make we advance a bit is welcome. Just want to expose this here, since IMHO, optimizations use to come when most of the things are working. I'm with Greg that for me most of this are post 1.0 issues to improve. But I don't think this will make a difference in Royale positioning or market penetration. I still didn't find a user or a client complaining me about size, or any optimizations (that does not mean are important or something we shouldn't pursue, don't interpret me bad, I think all is important). They complain always about components still not working (or still not created), features not implemented and most of the time issues with Bindings that worked in Flex code and not in Royale (I think Bindings is the main source of frustration in a migration) or they trying to add some CSS rule that makes compiler fail to compile.
---------------------------------------------------------------- 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
