Previous year, the Frontend Web Development Team of ours shed the habit of using Ruby. So, the obvious question is: which is better? Vue or Angular? Simply identify the one we chose as our frontend language.
VUE VS ANGULAR: OUR Needs
Being a tiny team, we required something properly documented and we could get familiar with ease. While testing Vue vs Angular, we needed to find something that was very familiar, as we would be working in an agile way. We desired a framework that enables us to develop working prototypes quickly. Having undertaken certain internal projects with Angular in the past, we came to a conclusion that Angular and React would suffice. We desired Angular as it satisfied our usual needs and also gave us the confidence that we could develop prototypes in CodePen and import them into our codebase easily. This looked impossible for us.
The issues regarding Angular
We built some humongous projects, such as Omstars and Keetoo, with Angular applications that we expanded from a mini working prototype to applications having zillions of monthly users. These are what we came to know all along.
Angular comprises certain performance-related hiccups and there are a lot of efforts needed to increase your project performance. But, the efforts are something which no one should comprise while building apps. For example, refrain from taking recourse to the ng-repeat directive or restricting your use of binding.
Two-Way Data Binding
This happens to be something I first thought would be revolutionary while building apps. A constant check regarding the $scope variable (data that can be utilized from anywhere in the project) and watcher in the DOM can be done when users go through your application. This check is enrolled with user events (such as click, scroll, key etc). It must be noted that this has had a profound impact on the page loading time.
Shifting to Vue
After consuming a few weeks for research and to compare frameworks (Angular2, React & Vue) and also developing some internal apps with React and Vue, we came to a conclusion that Vue, the framework, is simply meant for us. Given below are the reasons that prompted us to go for Vue.
The VUE Capacity
Vue’s performance is unarguably several notches better than Angular. Vue gives the project in the virtual DOM which is certainly quicker than the digest cycle in Angular (two-way data binding).
HTML AND CSS Expertise
All Frontend Developers need to familiarize themselves with HTML and CSS prior to dealing with other languages or frameworks. While operating on Vue you feel a bit of Deja vu which is hardly the case with what other frameworks provide. The knowledge we gained from HTML and CSS held us in good stead while moving to Vue.
A Convenient Learning Expertise
The last but not the least was how easier Vue was for us to get familiar with and this happened majorly due to the robust documentation and the community. As we built the internal applications with React, we got to know that it was very tough to get the basics right, however, with Vue, the documentation happened to be riddled with small code examples to enable you to go through every step along the way.
Vue VS Angular: The Finale
We at Winklix will be continuing our journey with the Vue because as a team we have invested a lot on it. Along the way, as we strive to make internal tools and undertake client projects we would like to share our progress as well. We have got a lot of things to talk about the Vue also. In our next rendezvous, we will be explaining how to establish a Vue project for the first time.