<story><title>Why we chose Vue.js</title><url>https://about.gitlab.com/2016/10/20/why-we-chose-vue/</url></story><parent_chain><item><author>iotscale</author><text>I started reading through the docs and found it very similar to Knockout.js. Is here anyone who used both to tell the advantages of Vue?&lt;p&gt;FYI, I&amp;#x27;m thinking about dropping Knockout because some performance problems I&amp;#x27;m having with a very specific use-case.</text></item><item><author>anonyfox</author><text>As someone who went through the complete frontend hype-trains (jquery, backbone, angular, ember, react, all in production): Vue.js 2.0 with single file components is exactly what everyone looks for desperately.&lt;p&gt;- performance: faster than react now&lt;p&gt;- learning curve: a few hours from scratch&lt;p&gt;- getting started: cli-tool for initial scaffold &amp;amp; configuration&lt;p&gt;- components: simple .vue files with a &amp;lt;template&amp;#x2F;&amp;gt;, &amp;lt;script&amp;#x2F;&amp;gt; and &amp;lt;style&amp;#x2F;&amp;gt;. Super easy to get going, no need for JSX&lt;p&gt;- &amp;quot;official&amp;quot; packages for routing, ajax and state management. No wasting of days for choosing every tiny package for days&lt;p&gt;- vuex 2.0 is one of the cleanest flux implementation i&amp;#x27;ve seen in the last year&lt;p&gt;... and much more. Give it a try with the full webpack template of the cli tool!</text></item></parent_chain><comment><author>holon</author><text>I&amp;#x27;ve used both Knockout and Vue for frontends that needed to render reasonably large amounts of disparate elements with near real-time updates, so I think I can answer this. Knockout is nice but feels closer to jQuery in that it requires a lot more discipline on the behalf of the developer to organise and maintain code. Things like ObservableArrays means dealing with another layer of abstraction; the wonderful thing with Vue is that it&amp;#x27;s just native JS objects all the way down. It also has a better structured child&amp;#x2F;parent component model with event flow, not to mention being much faster for rendering. I would also recommend Vue over Knockout.</text></comment>
<story><title>Why we chose Vue.js</title><url>https://about.gitlab.com/2016/10/20/why-we-chose-vue/</url></story><parent_chain><item><author>iotscale</author><text>I started reading through the docs and found it very similar to Knockout.js. Is here anyone who used both to tell the advantages of Vue?&lt;p&gt;FYI, I&amp;#x27;m thinking about dropping Knockout because some performance problems I&amp;#x27;m having with a very specific use-case.</text></item><item><author>anonyfox</author><text>As someone who went through the complete frontend hype-trains (jquery, backbone, angular, ember, react, all in production): Vue.js 2.0 with single file components is exactly what everyone looks for desperately.&lt;p&gt;- performance: faster than react now&lt;p&gt;- learning curve: a few hours from scratch&lt;p&gt;- getting started: cli-tool for initial scaffold &amp;amp; configuration&lt;p&gt;- components: simple .vue files with a &amp;lt;template&amp;#x2F;&amp;gt;, &amp;lt;script&amp;#x2F;&amp;gt; and &amp;lt;style&amp;#x2F;&amp;gt;. Super easy to get going, no need for JSX&lt;p&gt;- &amp;quot;official&amp;quot; packages for routing, ajax and state management. No wasting of days for choosing every tiny package for days&lt;p&gt;- vuex 2.0 is one of the cleanest flux implementation i&amp;#x27;ve seen in the last year&lt;p&gt;... and much more. Give it a try with the full webpack template of the cli tool!</text></item></parent_chain><comment><author>LaurentVB</author><text>Exactly my thought when I tried Vue.js: on the surface, it&amp;#x27;s knockout with some react-inspired additions that make it faster. I loved being able to pick up Vue.js and make something that just worked in 30 minutes.</text></comment>