6 Reasons to use Vue.js
Lynne Apr 15
Cover image by Clément H on Unsplash
I recently started working with Vue.js, and so far it has been one of the most enjoyable frameworks to learn. It’s very easy to set up and you can build something simple very quickly. I have had a so much fun with it recently, and felt the need to write this post and share some of the reasons I think people should give it a try!
With Vue, you can write an app very quickly and run it straight from the browser, or you can build a complex application using ES6, JSX, components, routing, bundling etc if you want to.
It gives you the freedom to structure your application in a way that suits you, there is no ‘right’ way.
The Vue documentation is very detailed, easy to understand, and includes various code examples. It also has a good, growing community of developers that can offer help when needed.
Can be used for simple and complex applications
For larger, more complex applications you can use Vuex for state management and routing. A key difference between using Vuex and using Redux/Flux with React for example, is that Vue’s companion libraries are officially supported and kept up to date with the core library. Redux and Flux came from the React community and is not tied to React.
During the transition process, Vue adds and removes classes on components/elements. It has 6 different classes which you can then customise in Sass to handle timing, and the start/ end styles of the transition.
It is fun!
In summary, here are some of the advantages of using Vue.js:
- It is a stable progressive framework
- Easy to learn and understand
- Simple and flexible
- Uses MVVM architecture
- Comprehensive documentation available
- Focus on organisation / project architecture
- Can be used for simple and complex applications
- State management is simple and intuitive
- Provides a number of ways to use transition effects
- It is a lightweight framework in comparison to React or Angular (around 20-30kb in size)
- It is fun!
Originally posted on http://www.lynnefinnigan.com/blog/