I make a web application with a long-term perspective. I decided to initially use Angular 2, but I didn’t like that it is too massive, it creates a lot of files and directories, and also installs a lot of modules that I don’t need (and are needed only for Angular 2), thus it does not fit in the general architecture of the application. And for the basis of my application, I will not take Angular 2, since its role is far from being paramount. But I now remembered that the first angular is simply connected with a reference and works immediately. But the question arises, and Angulyar 1 is generally a good product, otherwise I read about the enormous advantages of Angulyar 2, over my younger brother, that the question arises whether it is worth using Angulyar1 at all? Or is it better to get by with Orthodox jQuery and not fool yourself? Or maybe there is some kind of unpretentious framework (library) just to connect it with a reference and not assemble it in parts, not to upload any additional features, but just sit down with what I need?

  • 2
    As the project grows with Angular 1, the pain will begin. With the second simpler, its modularity is not a problem, on the contrary, you should not be afraid of it. In terms of something smaller, I have used KnockoutJS for a long time, maybe it will suit you, but I do not know how it is developing now. And a small note, Angular is a framework, and all sorts of jQuery and KnockoutJS are just libraries. - Umed
  • one
    If the framework "does not fit into the overall architecture of the application," then it is clearly not suitable, or the architecture is chosen incorrectly. As rightly noted @Umed - JQuery is just a library (ideologically almost opposite to Angular2’s approach, since DOM’s direct manipulation is contraindicated in 99% of cases), it doesn’t impose any approaches or concepts on you. Angulyar is another matter, you follow certain rules, and you get magic and pleasure from modules, components and Taipscript for the company :) - Dimanoid
  • one
    And about the size. We have ~ 200 files in the project (1.2mb) of the code, this is without any assets and global styles. The output of a production build with AOT is 170Kb bundle. In modern times, in my opinion, very modestly - Dimanoid
  • @Dimanoid, and how to choose the architecture correctly? - Bim Bam
  • @Bim_Bam I think this is a separate philosophical question :) I just wanted to say that if the architecture is known, but the tool does not fit ... one of the two makes sense to change. - Dimanoid

0