Sounds reasonable. IMO, the key advantage of Royale is that it requires less
touching of your code, especially touching by transcoding to a less structured
language. That is just an invitation to new bugs. Sure there will be plenty
of new bugs in the emulation components, but there are many more people
exercising those code paths so some of those bugs will be found and fixed by
others. If you touch your code, then all bugs have to be found and fixed by
you.
My 2 cents,
-Alex
On 7/13/18, 1:54 AM, "chembali" <chemb...@hotmail.com> wrote:
I have a meeting with the management tomorrow. I will try to convince them
without spending time on the POC if possible. Here is the high level plan
that I am going to present to them.
The plan is to perform the migration component by component using emulation
wherever needed. I will also consider using the new Royale APIs if the
emulation does not work for some reason. The third party libraries will be
migrated to the JS libraries.
I am putting together detailed plan for the individual component migration.
My developers can also get involved and take ownership of components and
start the migration process. Please let me know if you see any issues with
this approach.
--
Sent from:
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C93dee51c05234043832508d5e89e394d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636670688621976774&sdata=nVImt9kPSoPI4IXiYVSQ9ga5sHqQ%2Bpiuc2EHhY8H1Fc%3D&reserved=0
