Initial impressions of VueJS
Important: The information in this article is over 12 months old, and may be out of date or no longer relevant.
But hey, you're here anyway, so give it a read see if it still applies to you.
I love smarter ways to do things.
Around 2 years ago, I had a bit of a play with React, but found it never really had the right way to fit in to my existing projects without rethinking other parts. I loved the idea and the promise, but didn't like the framework.
But then I started having a tinker with VueJS. And was really impressed.
One of the first things that grabbed me was how I could choose to implement it - there's obviously the all-in Single Page Application (SPA) approach, but not every project lends itself to this. VueJS allowed me to enhance a more traditional website with only parts written with VueJS. This was a great way to start learning and developing with VueJS, and seeing what it can do for me as a developer.
One of my recent jobs has used a number of VueJS elements - the site's notification system, a chat interface, and a booking management interface. And showed two things:
VueJS (and the way it manipulates the DOM) is superb, and
I need to consider if jQuery is really necessary
VueJS enables me to make interactive interface elements with what I see as being smarter code. I can show or hide sections based on a data element of the VueJS instance. I can update an array of items and have the DOM just magically update too. Love it.
So do I still need jQuery? Well I've been using jQuery for years, so am really comfortable with it. But is it needed? There's still pros and cons there, but that's another topic.
In my recent learnings and experiments with VueJS, I've seen different ways to doing what I have been doing with jQuery, so am looking forward to evolving my front end application development and get a bit more elbow deep with VueJS, and even the SPA approach too.