Hi Mayur, I have answered questions like this before. spoiler, there is no definite answer, but I will try and provide you with some guidance. Angular 1.x and JQ can coexists quite fine next to each other in a single application. You don't have to expect any problem there. There is this other thing, that is called single source of truth. That means, that if you need to maintain your data in separate places, you end up in a maintenance nightmare. In angular there no such problem, there is just data, and the DOM will follow the change in the data. So the DOM is the *result*. In JQ apps, most of time the data you want to manipulate is scattered all over/into the DOM. While this works, it's not an ideal situation. And there is the problem, If you need to exchange data between both way's, it becomes hairy quite quickly. You probably will find out quickly then it's quicker to rewrite parts in angular then it is to create such an inter-op.
Does that help you a bit? Want me to elaborate on any of this? Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
