This is my first post in the series of posts I’ll be doing about Learning Angular 2. In this post,I’ll briefly talk about the origin Angular _2, and compare Angular 2 with some other development tools and frameworks I have used thus far._
In contrast to an MVC (model-view-controller) framework like Java Spring, Ruby on Rails with HAML, I would say Angular 2 is a model-view-whatever framework. Yes, it is sole purpose is to write the client-side of applications and the server-side operations can be done any language and Angular 2 does not care about it. The data is communicated through a REST API, which would be a topic for another blog post. Nevertheless, assuming data is transmitted through GET or POST requests, Angular 2 handles the view through the use of components as opposed to a specific view being rendered by classical MVC frameworks.
In Angular 2 an application is a tree of loosely coupled components. For example, as you are reading this blog notice that the Navbar, Blog container, Sidebar, and Footer can each be visualized as separate components. Using the categories the navbar or clicking the next button you can navigate through different blog posts without reloading the entire page. The next blog would just float into the blog container area leaving the other components in its place. This creates a single page application where the user’s experience is much richer as their views are not interrupted by page reloads.
In the next post, I will talk about the project I’d be working on this summer with other interns and how Angular 2 will come into play.