8

I have been using JavaScript and jQuery for quite a while now and want to extend my skill set further, during my search I came across two popular names Angular and Backbone and while reading about them I found one line common in both them which somehow also seems to be their USP i.e.

It is designed for developing single-page web applications

This makes my confused.

  • What is that I cannot do with JS or jQuery and I would require these?

  • I have created web application on single page, where users can perform CRUD operations on single page through asynchronous calls so why so much importance of for these others libraries?

And as a middle level web developer who has have good hands on JS is it right path to move to these two or here is something else I should look into before these?

Please help?

Maven
  • 14,587
  • 42
  • 113
  • 174
  • Have a look at [Understanding MVC And MVP For JavaScript And Backbone Developers](http://addyosmani.com/blog/understanding-mvc-and-mvp-for-javascript-and-backbone-developers/) – osahyoun Dec 04 '13 at 12:42
  • possible duplicate of [Angular.js vs Backbone.js](http://stackoverflow.com/questions/6548826/angular-js-vs-backbone-js) – fdomig Dec 04 '13 at 12:47
  • This might be helpful at least from a jQuery to Angular approach. http://stackoverflow.com/questions/14994391/how-do-i-think-in-angularjs-if-i-have-a-jquery-background – lucuma Dec 04 '13 at 12:52
  • Another helpful post on the subject. http://stackoverflow.com/questions/18414012/why-use-angularjs-instead-of-jquery/20362291#20362291 – m59 Dec 11 '13 at 06:25

3 Answers3

7

Structure.

In an ongoing project that started about 4 years ago we built the front end with jQuery. We were able to do just about everything that we needed creating several single page applications that were quite functional.

As the project progressed and the code base grew we started experiencing some major problems with maintainability of the code. We ended up with hundreds or thousands of lines of JavaScript code per page in a tangle that was almost impossible to navigate. This could have been avoided if we were more careful of course but at the time we focused on making sure the back end architecture was robust.

Many years ago the community learned that code needs structure to be maintainable. We developed MVC patterns, multi-tiered applications etc. But JavaScript was never a big player in the field and we largely ignored it.

Over the last 6 months or so we introduced Angular into the project and started sorting out some of the mess in the project. The results are remarkable. Not only is the code simpler and easier to create, the structure makes it easier to implement tests, easier to maintain and generally a huge improvement over what we had before. We still use jQuery but now we have been burnt by the lack of structure and know a thing or two about the architecture of a JavaScript application. Angular and its like provide you with the tools to architect a good application.

Vincent Ramdhanie
  • 102,349
  • 23
  • 137
  • 192
2

When you are creating larger scale web applications it is wise to check out Backbone, Angular or perhaps Meteor. jQuery supports neat tricks, but it does not help you structure your code in a maintainable way. Larger scale web apps build on jQuery need their own vision on how to separate the code into layers with their own responsibility. The other frameworks give more support.

I would suggest checking out at least one of the libraries. Perhaps you eventually won't use them, but it will benefit how you work in jQuery.

Raymond
  • 3,630
  • 2
  • 19
  • 22
0

Well Now a days there has been quite a hype about Angular.js and especially SPAs (Single Page Applications). Well to be honest, I had the same question in my mind about a month ago when my team decided to shift from Jquery to Angular.

Whenever it comes to Jquery, one of the first thing that comes in our mind is the DOM manipulation. While using Jquery we always think of manipulating the DOM. Show/hide elements, animating elements, getting data from tags you name it. But Angular offers something more than that. It offers you an architecture, a way to structure your applications at the front end.

So whenever you go for Angular.js, change the way you think about creating web applications (and believe me its worth it). Most of Angular's structure uses the concept of Dependency Injection which is a neat way to maintain your code.

Backbone is only a library whereas Angular.js is a complete framework to create and manage Single Page Applications

Talking about the fact that Angular.js should be used when we are creating large scalable apps, it is true. In my case the team I work with is full of Jquery Ninjas. We have been creating a great app for the last 3 years and believe me it became difficult for us to maintain and debug thousands of lines of Jquery. This is the main reason we have decided to revamp this app into Angular.

Kindly see some of these Helpful links. You will get a better idea.

  1. http://net.tutsplus.com/tutorials/javascript-ajax/3-reasons-to-choose-angularjs-for-your-next-project/
  2. "Thinking in AngularJS" if I have a jQuery background?
Community
  • 1
  • 1
Talha Masood
  • 993
  • 1
  • 7
  • 22