Structure.
In the current project, which began about 4 years ago, we built an interface with jQuery. We were able to do almost everything we need, create several applications with one page, which were quite functional.
As the project developed and the code base grew, we began to experience some serious problems with maintainability of the code. We ended up with hundreds or thousands of lines of JavaScript code per page in a ball that was virtually impossible to move. This could have been avoided if we had been more careful, of course, but at a time when we focused on ensuring that the architecture of the rear was reliable.
Many years ago, the community found out that the code structure needed to be repaired. We have developed MVC templates, layered applications, etc. But JavaScript has never been a big player in this area, and we basically ignored it.
Over the past 6 months, we introduced Angular to the project and began to sort out some of the mess in the project. The results are wonderful. This code simplifies and simplifies the creation, simplifies the implementation of tests, simplifies their support and, as a rule, significantly improves what was before. We still use jQuery, but now we are burned out due to lack of structure and we know something about the architecture of the JavaScript application. Angular and how to do this will provide you with tools for archiving a good application.
Vincent ramdhanie
source share