How we do Vue at GitLab: one year later
At my last job we did a comparison between Vue and React before rewriting a major frontend application.<p>We did a POC in both React&#x2F;Vue and ended up using Vue mainly due to the following reasons:<p><i>Single File Components</i><p>Single file components (.vue files) is the best thing about Vue.
I understand this might be a personal preference, but we wanted to avoid CSS-IN-JS.
Our designer could churn out neat html&#x2F;css, but was a beginner in Javascript.
With Vue&#x27;s single file components, he could also hack parallely with us while iterating on html&#x2F;css.<p><i>Standard &#x2F; Official way of doing things</i><p>This again is a personal preference but Vuejs comes with a recommended way to do a majority of things.
Vuex(state management) and Vue-Router are provided&#x2F;maintained by same Vue core team.<p>React at times can be overwhelming for beginnners, just because of the amount of choice available<p>Example:<p>Google Search for &#x27;React CSS style&#x27; [<a href="https:&#x2F;&#x2F;www.google.co.in&#x2F;search?q=react+css+style" rel="nofollow">https:&#x2F;&#x2F;www.google.co.in&#x2F;search?q=react+css+style</a>] points to a bunch of links all of which link to valid solutions, but I have to go through a few of them before I get what I am looking for.<p>Similar search for &#x27;Vue CSS style&#x27; [<a href="https:&#x2F;&#x2F;www.google.co.in&#x2F;search?q=vue+css+style" rel="nofollow">https:&#x2F;&#x2F;www.google.co.in&#x2F;search?q=vue+css+style</a>] all top links lead to official documenation on vuejs.org.<p><i>Excellent documentation</i><p>Also, as a team we were primarily writing Angular 1 when we decided to choose a frontend framework for newer projects.
I feel this also made our transition to Vue easier vis a vis React