At that time, we were doing all the web work using pure HTML, CSS, JavaScript, and php for the backend. While this was efficient for our developers because they knew it well, the promise of a framework making things more consistent with reduced development time sounded good. At least good enough for me to take a deep look at Angular, React, and Vue.

My conclusion was that Vue was easier to learn and offered some readability improvements over Angular and React. Vue used fewer lines of code and was, in my opinion, more readable.

So, we started a couple of new projects using Vue. It went fairly well. But like all new things, it had some issues. It reminded me of every time I tried to adopt something new from Microsoft: I got 90% of the way in far less time, but it took a much longer time to resolve some of the nuanced issues where the frame actually gets in the way.

This is why, over the many years I''ve been writing code, I''ve always come back to the basics like C, C++, HTML, CSS, JavaScript, and php. You can''t get boxed into a corner when you use the basics. 

Ultimately, I went back to not using Vue when they released Vue version 3. Constantly having to learn a new way of doing things and rewriting 10s of thousands of lines of code is not productive.

Maybe it didn''t work out because these were very large projects. Maybe I just don''t like the ground shifting under me and my team due to the last efficiency and time costs. No matter what the reason, Vue didn''t ultimately become a framework that worked for me./

Don''t get me wrong: I love many things about Vue. But those didn''t offset the downsides.