If we have worked on templates in other JavaScript framework\/library like Note that Angular processes on DOM nodes instead of strings contents<\/strong>.<\/p>\n There are basically two phases in which Angular<\/a> does this, The concept of Backbone<\/code> and jQuery<\/code>, they process the template as a string and result as a string. We have to inject this result string into the DOM<\/code> using innerHTML()<\/code> or some other way, because there is no two way binding that needs to happen, we render the markup once, and do it again when any changes are there. But it is not the case in AngularJS.<\/p>\nThe AngularJS way<\/h2>\n
AngularJS<\/code> processes the template in entirely different way. It works directly on HTML DOM<\/code> fragments(in memory) rather than strings and manipulates it as required. It uses two-way data-binding between model and view to sync our data.<\/p>\ncompile<\/code> and link<\/code>.<\/p>\ncompile<\/code> and link<\/code> comes from C<\/code> language, where you first compile the code and then link it to actually execute it. The process is very much similar in AngularJS<\/code> as well.<\/p>\nThe Process<\/h2>\n