greg-dove commented on issue #648: Tasks to Reach 1.0 URL: https://github.com/apache/royale-asjs/issues/648#issuecomment-570821762 @carlosrovira I will go into a bit of detail about why I think the way I do about React etc., but I don't really want to 'promote' it :) just to speak plainly about why I think the way I do. Please don't doubt my commitment to Royale. Anyway, I will say just a few things: I think @piotrzarzycki21 expressed some of my thoughts. When I look at the local React community I see it is larger and more active locally than we were 10 years ago with Flash/Flex, just observing the number of events and participation levels (I joined some local online community groups a few years back so see the activity). The community is self-sustaining/self-supporting at many levels. At a technical level, (and less specific to React) many of the original advantages that FlexJS would have had if it were released 7-8 years ago (in current state of Royale, for example) have since been eroded. JS development is no longer the 'wild west' that we used to think of it as Flex developers back then. It is now disciplined, can be strongly typed (even at runtime for debug builds with React), and is easy to setup for testing, etc. We have focused a lot on 'smallest possible code' with Royale. While that is definitely given consideration in the projects I worked on, I have seen far more emphasis on code quality and maintainability (think: Flex PMD/SonarQube etc), and all of this support seems well integrated into workflows and IDEs. Some of these changes to js development may have been natural evolution of js development itself, but I think certain practices also became emphasized after NodeJS and with more back-end developers entering the full stack category, bringing with them some of their 'quality' practices (sometimes this does not always work well in front-end, but I think in general it has advanced JS development a lot). The technical reality is that because JS development has evolved, as3 has less advantages over JS than it did 7-8 years ago. So that is something I think adds a bit to what Piotr said. Outside that general impression, React includes functional coding style, with emphasis on immutable global state, so people who are committed to that paradigm will probably find it strange to go back to more 'loose' object oriented approach. I can say that I found it strange to 'get my head' into React paradigm, but once you do, it is interesting to know about. The work I did with React was coding directly in es6+, so the code itself is actually not bad. I only know for sure what I have experienced and I focused more on Royale during the last year (I did do *some* React/RN coding, but much less), so I am sure things continue to change and evolve for React/ReactNative - 'moving fast and breaking things' was sometimes a frustrating part of the experience with React Native particularly, it was not all easy!) but I assume coding in at least es6 might be considered 'minimum standard' now. It was being transpiled to es5 for IE11 support with what I was working on. But it can be more minified if es6 is retained in the output so that is another form of future proofing that we don't yet have. Another advantage for React is React Native. Obviously React itself could be used via WebView/Cordova etc similar to Royale. But React Native gives closer to 'native' performance and has 'view' and 'code' running on different threads. Until Royale has more targets to match that, I think that would also probably be used as a justification against us by React people. Again, this is again all just my opinion. Hopefully it is more clear why I think the way I do. I really don't want to talk more about React now :)
---------------------------------------------------------------- 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
