samedi 4 juillet 2020

The impact of frameworks on the site speed [closed]

I understand that frameworks exist to facilitate the development process and further support. But I have a question. How much does their presence affect the site's speed?

  1. Frames themselves are additional files (or strings in the case of working with Babel). This means that the site needs to upload more information. Plus, not all sites realize the full potential of the framework. This means that some of the information is loaded in vain.

  2. The code executed by the framework is not executed directly. I mean, using $('.class').text('text') will call the framework functions, which will call other functions of the framework, and so on.

  3. And a special question about Babel. This compiler converts scripts to the old format, thus generating a huge amount of code. I don't understand the history of JavaScript, and I understand that more code doesn't equal slower work. But I think such generated code can also slow down the site.

I'm not trying to dissuade anyone from using frameworks. In frameworks we trust. I just want to understand what developers are sacrificing by increasing the speed of development.

P.S. I also think the situation gets worse when frameworks are layered. For example, to use Marionette.js needed Backbone.js, which requires an Underscore.js and jQuery.




Aucun commentaire:

Enregistrer un commentaire