Why We Chose Vue.js
If we had infinite time, willpower and nerve… our development stack would be rendered useless. We would code everything in assembly language… calligraphy style… on vellum… with quills. Thankfully, for those of us who like a challenge, we live in a world of constraints. This lack of time, money and attention span gives rise to questions about which tech to use. If you care about your project, your mental health and your time… this decision is important.
When choosing a framework, you're choosing a tone. You're choosing how you will communicate to other developers. You're choosing a shared mental model.
At Mempkin, we've decided to go with Vue.js. As a tiny, self-funded startup in Birmingham, UK we have two constraints that big companies don't have: a lack of resources in hiring/training developers and a lack of resources for managing complexity. Vue's form, value and function fits these needs. The Vue.js community has put a lot of effort into being as accessible and practical as possible. Which gives us extra leverage in our codebase and in training local developers.
The decisive factor was the tone and approach of Vue and it's community, it's pragmatic, well thought out and is not at all dogmatic.