A room with a Vue
I’ve spent a lot of time looking for a framework to replace Angular. It’s not so much that there was anything wrong with Angular, but the move from the Angular 1.x architecture to what came after it encouraged me to take a look around and see what else was out there. If I was going to have to essentially learn a new framework (Angular 2–7 were different enough), I might as well make sure I had the one that I wanted to bet the mental farm on.
This started a journey for looking at the competing frameworks Vue and React. I didn’t have a need to make an immediate decision, and I wasn’t driven by a need to get a job writing web pages or be concerned with whether or not my boss or team would be happy with my decision so I could take the time to look at a framework and see what I really liked.
All this time I had pretty much ignored Vue. I don’t know why, but something about Vue and the way it was marketing itself just always made me feel like it was an “also-ran” so it always stayed at the bottom of the heap. Some of my initial looks at the code just didn’t excite me. This may have been the universe just forcing me to wait because while I was playing around with all the other frameworks, Vue got really really good! A few months ago I decided that it was time to do my due diligence and try it out and I was amazed with what I’d found. Here was a framework giving me all the data-binding, virtual DOM, and a tag-centric syntax. I like the tag-centric syntax. It looks clean and organized to my eye. For me it’s easy to read and it’s community and tools… well that was just better than anything I’d seen from anything else. I was really surprised that it wasn’t corporate-backed like React and Angular. Throw in a Vue Material component library and I was sold.
So now I’m a Vue convert. I’ll do my normal thing and start making tutorials and videos for building stuff with Vue and move on. Between Vue, Python, Flask, Lambda, and Keras I pretty much have a new stack.