@Incubatio "I feel royale is meant mostly for former flex user and flex app scope, am I wrong ?"
I don't think so. For me (active Royale developer), is to get the best things we had in Flex and get the best things we have in the current HTML/JS/CSS ecosystems. Just an example. Royale benefits of CSS in browsers that I think is by far better than what we had in Flex. In the other side, to complement what @Harbs already said. We need more contributors to enhance compiler and core things. What we have have now is what the current team could bring. More hands contributing will mean better output and a better technology that fit more use cases. @matrix3d I think instead to go a step backwards and go a dead tech (FlexJS) you should go with us and make the changes you consider in Royale to get what you need. Finally, I expect, now that we are getting Royale generate most of what users need in HTML, people could join us to make a new target possible: #WASM, I think you guys could contribute to that and make this happen. Hope you could consider this offer :) just my 2... ;) Thanks [ Full content available at: https://github.com/apache/royale-asjs/issues/260 ] This message was relayed via gitbox.apache.org for [email protected]
