What makes Angular and Backbone different from jQuery?

I have been using JavaScript and jQuery for a long time and want to expand my skillset further, during my search I came across two popular names Angular and Backbone , and, reading about them, I found one line common in both cases, which somehow also seem to be their USP, i.e.

It is designed for developing single-page web applications

It bothers me.

  • What I can not do with JS or jQuery and I would require them?

  • I created a web application on one page where users can perform CRUD operations on one page via asynchronous calls, so why is it so important for these other libraries?

And as a mid-tier web developer who has good hands on JS, is this the right way to move on to these two, or is there something else I should learn before that?

Please, help?

+8
javascript jquery angularjs
source share
3 answers

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.

+7
source share

When you build larger web applications, it’s worth checking out Backbone, Angular, or perhaps Meteor. jQuery supports neat tricks, but it does not help you structure your code in a user-friendly way. Large-scale jQuery-based web applications need their own vision of how to split code into layers with their own responsibility. Other frameworks provide great support.

I would suggest checking at least one of the libraries. You may not end up using them in the end, but it will be useful how you work in jQuery.

+2
source share

Well, now the other day there was pretty hype about Angular.js and especially SPA (Single Pages Applications). Honestly, I had the same question that I was thinking about a month ago when my team decided to switch from JQuery to Angular.

Whenever it comes to jQuery, one of the first things that come to mind is the DOM manipulation. When using jQuery, we always think about manipulating the DOM. Show / hide elements, animate elements, receive data from tags that you name. But Angular offers something more. It offers you the architecture, a way to structure your front-panel applications.

So whenever you go to Angular.js, change the way you think about building web applications (and trust me, it's worth it). Most Angular structures use the Injection Dependency concept, which is a neat way to maintain your code.

The backbone is just a library, while Angular.js is the complete framework for creating and managing single page applications

Saying that Angular.js should be used when we create large, scalable applications is true. In my case, the team I'm working with is full of Jquery Ninjas. We have been creating an excellent application over the past 3 years and believe that it has become difficult for us to maintain and debug thousands of jQuery lines. This is the main reason we decided to upgrade this app to Angular.

Please see some of these useful links. You will get a better idea.

0
source share

All Articles