Why Angular 2

Early this year, I began on a self-righteous (but approved, of course ūüėČ )¬†journey to make things right¬†for my project —¬†to break all shackles and limitations that the¬†team faces in working with older technologies, methodologies and guidelines. When I started off, my aim was¬†to make as minimal-but-essential changes to the system as possible, keeping in mind that¬†my¬†project is a live one, having at least 100 MegaBytes¬†of code, with around 16¬†developers contributed¬†to this application¬†—¬†in batches, of course¬†—¬†in¬†the past 8 years, each having their own signature style of coding.¬†Needless to say, there were more than a few tasks for research in this journey of mine.

One such, important analysis was to decide what UI methodology should the team adopt going forward. This blog post will focus on the analyses and decision-making process that made it happen and finally helped me decide on Angular 2.

Continue reading