DEV Community

Cover image for Moving From Angular to Vue : A vuetiful journey

Moving From Angular to Vue : A vuetiful journey

Hemant Rai on May 02, 2017

I work on a SaaS product which has several front-end portals and all of them were build on Angular 1. After more than 2 years in production, Angula...
Collapse
 
guillaumedoutriaux profile image
Guillaume Doutriaux

Thanks you for this article ! I was just wondering... before moving to VueJs, did you think about angular 2 as an option ?

Collapse
 
jmlane profile image
Jonathan M. Lane

I was wondering this as well.

Collapse
 
onekiloparsec profile image
Cédric Foellmi

The step going from "hello world" to "real world" (that is, here, an app with webpack + vue + vue-loader + vue-router + vuex) is where a framework shines, or not.

It is not only a matter of how fast you can setup a real world project, but also how fast you end up feeling confortable with that setup and producing app code, not setup code.

To me VueJS 2 succeeds at both very well, and I am not a front-end dev (is it an argument? :-).

P.S. Even if Vuejs is progressive, I've started my app right away with components and .vue files.

Collapse
 
hemantisme profile image
Hemant Rai

Couldn't agree more. The ease with which we were able to develop for production made us love Vue even more.

Not much time was lost in getting everyone up to speed. The hello world-ish app with all the bells and whistles was helpful in introducing everyone to Vue concepts and not much had to be changed when working with the production app.

Collapse
 
isavegas profile image
Leviathan Jeanis

What on Earth are you doing comparing Angular 1.x and Vue? Of course Angular 1.x is showing its age. At least use the correct name so people will know what you're talking about: AngularJS.

Collapse
 
oktav777 profile image
Octavian Lari

It drives me so mad when people don't know how to specify framework version correctly. Of course AngularJS (which is 1.x) will be worse than any new framework. Even devs said that, that's why they designed a new version from scratch...

Collapse
 
mobilunity profile image
mobilunity

Very interesting article, thanks a lot for sharing. Seems like there are more and more articles to tell us how Vue.js can be a good choice. No wonder it holds such a high (89%) satisfaction rate among developers that have used it. We also have a post about it with some samples of CVs of our Vue.js developers. Also, we are preparing an interview about the framework and I'll be happy to share it with you when it's finished.

Collapse
 
sebastienroul profile image
ROUL

Very good !
We are doing the same.
Two points draw our choice :
-smmoth curve learning

  • no type script Two points were problem
  • the "none séparation of concern" : everything in vue files was not possible for out TeamViewer
  • the "one file" contrôler : same above it was not possible for our team.

At the end we broke the "boilerplates" organisation to move to Real functional packages and everything is perfect.

Collapse
 
chathula profile image
Chathula Sampath

Grate article..but actually why u guys moved to vue instead of react? is it similarity of syntax like v-for etc?

If it is a much larger app react is the recommendation of most developers? is it true?

Collapse
 
tomerbendavid profile image
Tomer Ben David
  1. so angular2/4 solves the two way binding.
  2. angular2/4 encourages you to work with a transpiled language which can save time and bugs and eases new develoeprs and IDE better intellisense (like compile).
  3. angular2/4 has a standard routing and dependency injection out of the box.
  4. angular 4 is as fast or almost as fast as vue.js

I don't understand why then to choose vue.js is seems like only the starting rampup is high but then you have to reinvent the wheel which is already invented by angular4, what do you think?

Collapse
 
otijhuis profile image
Okke Tijhuis

Angular 4+ is much better than Angular 1, no doubt. I've been using it on a project for a while now and it has its own set of issues.

I like typescript but I only see it as documentation / improving the IDE experience. There are no runtime checks so you still have to be very careful.

RxJS is also very nice but I've seen most developers struggle with how to use observables properly. And they are everywhere in Angular.

While Angular 4+ will be great for a lot of applications, the "all batteries included" part can actually work against you. A lot of decisions have been made for you and trust me, once you're building a more complex/dynamic application you'll often be fighting against the framework. We've struggled with things that would have been simple with Vue (like highly dynamic components). And we still haven't found decent solutions for some of them. Most of them feel hacky.

Personally I'll avoid using Angular if I have the chance. It's just too restrictive for me.

Collapse
 
kzagoris profile image
Konstantinos Zagoris

Why you don't consider angular2? Is there any reason for that?

Collapse
 
dimpiax profile image
Dmytro Pylypenko

Thank you for sharing your experience, enough motivating to open Vue. :)

Collapse
 
esamcoding profile image
esam a gndelee

why you said : "Angular was already being highlighted as a risk going forward"?

Collapse
 
figonesia profile image
Igor

ThoughtWorks Technology Radar and many well-known front-end developers are discouraging any new project to start with Angular 1 (AngularJS) due performance issues and lack of support. This statement is not valid for Angular 2+ though