“ECMAScript 2015-2018 simplifies the approach for writing well-structured code”
JAXenter: The standard your company had developed differed from the official one. What were the main differences?
JAXenter: What were the greatest difficulties you faced in the re-architecting process?
When it comes to the re-architecting process, avoid the use of non-standard solutions if you can. Go for your own custom solution only if it is absolutely necessary.
JAXenter: Can you think of any tips for companies going through a similar adjustment process?
Olga Petrova: The main advice that we can share is to try to avoid the use of non-standard solutions if you can. Go for your own custom solution only if it is absolutely necessary, like it was in our case. And try to estimate the effort you would need to re-write it in advance. Another obvious tip is to encapsulate your custom extension because it reduces the modification time in the future. And always keep your eyes on new technologies and standards, and try to adapt your custom solution to align with industry trends faster.
JAXenter: In your opinion, what was the main takeaway of your talk at iJS 2019?
Olga Petrova: In my talk, I shared our architectural decisions, the technological background that influenced our decisions dramatically, as well as the pitfalls we encountered and the adaptations we made to align with standards used by the modern web community to ultimately re-build Ext JS, Sencha’s web application framework. I hope that attendees learned how to apply this experience and best practices we have learned to their own projects, and that it ultimately helped them navigate a better, more strategic approach that aligns with current technologies to properly build out their solutions.