Hi Scott, thanks for sharing. I think React is a good solution, as Flutter or others like Vue, Angular... nowadays we have enough options out there, and all of them allow us to reach our goals, so it's just a matter of "what you are more comfortable with".
As well not all Flex developers, or Royale developers are searching for the same needs. For example, I needed AMF and RemoteObject, and we needed to make it real in Royale. Nowadays, Royale is the only technology out there where AMF really works end-to-end without touching a line on the server side. For me that fact was key, since I could migrate from Flex, pushing a Royale version side-by-side to the Flex one to our users. Other options required us lots of work and changing server, so more problems, time and investment. As well for me Royale means to keep the same ordered mindset of declaring interfaces in MXML as I imagine of it, and for me that experience is invaluable in terms of productivity. I think JSX or other options are not as simple or elegant as MXML when I compare code. Of course, this could be just my perception. In my company we have as well projects in React and as I check code done when reviewing our repos (in PRs, direct commits,...), while is valid, for me still seems like a step back from what we had with Flex. Here's the full code (exposed to the community) of the widget app: https://github.com/codeoscopic/avant2-website My vision is the Royale programming model is far more easy, simple and elegant. Again just my perception, normal since I'm working for it each day to make it shine ;). Of course, Royale doesn't come for free, and we need as a community to be involved to get the most of it. Most of the times, when I see huge communities, I see very few people "following", "staring", making volume, but many few working to make it evolve, so while I understand is many important for people see "community volume", I'm for continue betting for Royale to make it grow in community and code and since I think it deserve the effort and of course...because I enjoy it! ;-) El dom., 9 ago. 2020 a las 12:57, Scott Matheson (<sc...@matheson.it>) escribió: > Carlos > I think the work you have done is outstanding, however as a > small developer, is there a real long team future, I know we always say > yes, but we where let’s down big time by Adobe with these poor management > of the flex issue and the abandonment of flex > > Flex is a great language, however most languages have a life expedience > > JS in versions , C in versions, python seems to be good long terms bets > > I started in this industry in 1980’s so I have seen lots of stuff come and > go > > IMHO royal is a side road that may run out if tar some time in the future, > then your back to start > > After looking are royal last you we spent the last year moving our app to > react it is very close to flex in a lot of ways > > Just me thoughts > > Scott > > > > Sent from my iPhone > > > On 9 Aug 2020, at 11:22, leokan23 <l...@best-web.gr> wrote: > > > > Hi Carlos, > > > > of course Royale was my first try back in version 0.7.2. The reason I > tried > > it was mostly for web but I had many issues starting with it. Piotr > helped > > me a bit to start but at the time my main issues where: > > > > 1. Documentation was scarce (there were mostly examples, not > documentation). > > 2. The first few times i tried to setup the sdk, I couldn't make it work. > > Actually Piotr spent like 50 minutes trying to setted up on my laptop a > few > > years ago. > > 3. Another issue for me was that I had to rewrite all the UI as Sparks > > emulation wasn't available. > > > > One of the things I am not sure how it works, is the mobile part (which > I am > > most interested for). In my understanding you need to use cordova which > > makes Royale comparable to Ionic, which is not the best option as it is > > basically a wrapped web site in an app. Not sure if you can export the > > Royale project directly to AIR apk or ipa. > > > > After Jewel was released, I thought about giving it another go, but due > to > > lack of time I never did. I am not sure if the issues above still stand, > but > > if you can clarify the mobile thing, I would be glad. :) > > > > > > > > -- > > Sent from: http://apache-flex-users.2333346.n4.nabble.com/ > -- Carlos Rovira http://about.me/carlosrovira
