A Vue To A Kill: Day 01 – What am I doing?

Recent developments at myClin have had me turn my attention to building a front-end framework for our web application. Our current framework is a bit dated and relies on templates written in JSPs to handle some of the heavy lifting. It has worked well for most of our lifecycle, however, it is not aging too well and its time to clean things up a bit.

Now you know the motivation. Let me take you through some of the things I have found out. This is mostly to document my journey through this, follow along as much as you like.

Although, I have known about Vue and other frameworks like Angular and React for some time, I never really dug deep and tried to build anything more than the obligatory “ToDo” apps that seem like a right of passage in a way. This was more or less due to lack of necessity. I did not really NEED Vue, or any other framework for that matter, to solve any of the problems in my personal or professional life. Believe me, I would have loved to do this sooner. But as anyone who builds software can tell you, it is not an easy ship to turn.

Why Did I Choose Vue?

While the debate about which front-end framework is best rages on in the world of web development, I want to make this disclaimer—I am not suggesting Vue is the best or even the framework anyone reading this should go with. It was the framework I chose as the best option for the problems we were facing, all the while considering the skills of others on the team as well as the ability to more easily plug-in third party vendors for collaboration.

There was some research before deciding to go with Vue. The opinions of my friends who are front-end and back-end devs were weighed and measured. I also found a good amount of info with some simple Google searches. Here are a couple of links I found useful while making this decision:





Getting to work on a real problem.

Now that I have a need for building something in Vue the whole approach changes. In this go-round I have requirements that need to be met. The framework needs to be easy to understand, spin-up, and deploy. This front-end will eventually have to plug-in to REST API and managed in some kind of containers. With this loose criteria I can roll up the sleeves and get started.