Homegrown Javascript frameworks - evil
I can even imagine how they appear. Need to write some simple function? Done! And here it is necessary to make one more? Get it! But what if we make a general version and put it in a separate file? Of course! And now let's make classes, and a special loader that will load only the necessary scripts on each page ... And here you need to make an asynchronous call ...
After a few years, it turns out that such a framework is simply impossible to maintain. Because it was written chaotically, there is no documentation, and the people who did this have not been working in this company for a long time. Correction of errors, the addition of new functionality, adaptation for a new browser are becoming very expensive. Sometimes such libraries even hinder the further development of the project.
If for typical tasks arising during the development of a web application, to use well-known JavaScript frameworks, such as Prototype, jQuery, mootols, a lot of maintenance problems will immediately disappear. These libraries are widely used, developed, have good documentation and examples. A large community will help solve most problems. If you find errors in such a framework, or you need to make support for a new browser, you need to wait for the new version, and not pay for the time to upgrade your unique development.
')
Sometimes you don't need to reinvent the wheel at all.
UPD: This is a commercial development, when there are requirements and deadlines.
UPD2: If you have made a cool framework for internal use, with support for different browsers, extensive documentation and cool design, I take off my hat. This topic is not about you.
After a few years, it turns out that such a framework is simply impossible to maintain. Because it was written chaotically, there is no documentation, and the people who did this have not been working in this company for a long time. Correction of errors, the addition of new functionality, adaptation for a new browser are becoming very expensive. Sometimes such libraries even hinder the further development of the project.
If for typical tasks arising during the development of a web application, to use well-known JavaScript frameworks, such as Prototype, jQuery, mootols, a lot of maintenance problems will immediately disappear. These libraries are widely used, developed, have good documentation and examples. A large community will help solve most problems. If you find errors in such a framework, or you need to make support for a new browser, you need to wait for the new version, and not pay for the time to upgrade your unique development.
')
Sometimes you don't need to reinvent the wheel at all.
UPD: This is a commercial development, when there are requirements and deadlines.
UPD2: If you have made a cool framework for internal use, with support for different browsers, extensive documentation and cool design, I take off my hat. This topic is not about you.
Source: https://habr.com/ru/post/54017/
All Articles