<story><title>Migrating from Vue 2 to Svelte</title><url>https://escape.tech/blog/from-vue2-to-svelte/</url></story><parent_chain><item><author>randomsearch</author><text>In what way is being on Vue 2 painful? Using it in production, zero problems, everyone understands it, does everything we need.&lt;p&gt;Plan to migrate to Vue 3 for the nice to haves and to keep up to date, but Vue 2 is not painful at all.&lt;p&gt;Considered React but I think Vue will be more productive for the team as a whole in the long term. Vue is more intuitive, better designed, and structured. But totally understand React has a larger ecosystem - we’ll just be building more stuff in house so understanding our own code will be more important than having a larger choice of dependencies.&lt;p&gt;Did take a look at Svelte, agree with you.</text></item><item><author>for1nner</author><text>The very first paragraph leads me to believe this is just a rewrite into svelte for the sake of it - I get it, Svelte is the new hotness on the FE-js-block, but this entire post stinks of &amp;quot;someone on the dev team advocated and fluffed enough figures to convince us. So now we&amp;#x27;re going to tell you why it was the right choice!&amp;quot; I say all this pretty confidently as someone currently maintaining a massive legacy vue2 app which we are currently rewriting into... *checks notes* React. Because we thoroughly vetted and PoC&amp;#x27;d how we&amp;#x27;d do it in Svelte and in Vue 3. The former is utterly untenable for an actual product-serving business - it is a pre-release, actively-developing product. Vue 3 is great, I highly recommend reacty-folks or frontend devs try it. We wanted the larger ecosystem (and boo to us for not being brave enough to support the growing vuecosystem).&lt;p&gt;The framework is so new, trying to justify your decision based on State of JS surveys over the last three years is asinine at best - svelte&amp;#x27;s own UI framework[1] is not even at 1.0 (has only recently been renamed to sveltekit).&lt;p&gt;Furthermore, there&amp;#x27;s a literal migration guide[2] to bring your app from vue 2 to 3. It&amp;#x27;s not easy. It&amp;#x27;s not painless. But being on vue 2 is equally painful. I&amp;#x27;m also not sure what documentation or development this person is referring to because &amp;quot;restricted global access&amp;quot; is just patently false for both vue 2 and 3 - I don&amp;#x27;t even know what to cite here because it boggles my mind so thoroughly that I can&amp;#x27;t even conceive where you would come up with that &amp;quot;fact.&amp;quot; Is this someone who&amp;#x27;s never opened their root app file? The place where one can pipe anything from decorators (and yes, enums???) to entire packages &lt;i&gt;globally&lt;/i&gt;?&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;kit.svelte.dev&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;kit.svelte.dev&lt;/a&gt;
[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;v3-migration.vuejs.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;v3-migration.vuejs.org&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>Oddskar</author><text>As someone working in a large Vue 2 app:&lt;p&gt;- Very poor typescript support.&lt;p&gt;- Poor performance (compared to Vue 3).&lt;p&gt;- Ecosystem has already started lagging behind (e.g. Vue Testing Library for v2 has out of date dependencies, and no one is actively maintaining it)&lt;p&gt;- Nuxt 2 hasn&amp;#x27;t made any releases in ages.</text></comment>
<story><title>Migrating from Vue 2 to Svelte</title><url>https://escape.tech/blog/from-vue2-to-svelte/</url></story><parent_chain><item><author>randomsearch</author><text>In what way is being on Vue 2 painful? Using it in production, zero problems, everyone understands it, does everything we need.&lt;p&gt;Plan to migrate to Vue 3 for the nice to haves and to keep up to date, but Vue 2 is not painful at all.&lt;p&gt;Considered React but I think Vue will be more productive for the team as a whole in the long term. Vue is more intuitive, better designed, and structured. But totally understand React has a larger ecosystem - we’ll just be building more stuff in house so understanding our own code will be more important than having a larger choice of dependencies.&lt;p&gt;Did take a look at Svelte, agree with you.</text></item><item><author>for1nner</author><text>The very first paragraph leads me to believe this is just a rewrite into svelte for the sake of it - I get it, Svelte is the new hotness on the FE-js-block, but this entire post stinks of &amp;quot;someone on the dev team advocated and fluffed enough figures to convince us. So now we&amp;#x27;re going to tell you why it was the right choice!&amp;quot; I say all this pretty confidently as someone currently maintaining a massive legacy vue2 app which we are currently rewriting into... *checks notes* React. Because we thoroughly vetted and PoC&amp;#x27;d how we&amp;#x27;d do it in Svelte and in Vue 3. The former is utterly untenable for an actual product-serving business - it is a pre-release, actively-developing product. Vue 3 is great, I highly recommend reacty-folks or frontend devs try it. We wanted the larger ecosystem (and boo to us for not being brave enough to support the growing vuecosystem).&lt;p&gt;The framework is so new, trying to justify your decision based on State of JS surveys over the last three years is asinine at best - svelte&amp;#x27;s own UI framework[1] is not even at 1.0 (has only recently been renamed to sveltekit).&lt;p&gt;Furthermore, there&amp;#x27;s a literal migration guide[2] to bring your app from vue 2 to 3. It&amp;#x27;s not easy. It&amp;#x27;s not painless. But being on vue 2 is equally painful. I&amp;#x27;m also not sure what documentation or development this person is referring to because &amp;quot;restricted global access&amp;quot; is just patently false for both vue 2 and 3 - I don&amp;#x27;t even know what to cite here because it boggles my mind so thoroughly that I can&amp;#x27;t even conceive where you would come up with that &amp;quot;fact.&amp;quot; Is this someone who&amp;#x27;s never opened their root app file? The place where one can pipe anything from decorators (and yes, enums???) to entire packages &lt;i&gt;globally&lt;/i&gt;?&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;kit.svelte.dev&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;kit.svelte.dev&lt;/a&gt;
[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;v3-migration.vuejs.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;v3-migration.vuejs.org&amp;#x2F;&lt;/a&gt;</text></item></parent_chain><comment><author>jakewins</author><text>Isn&amp;#x27;t the reasoning to migrate literally the first sentence in the blog post?&lt;p&gt;&amp;gt; After using Vue 2 as our front-end framework for almost two years, it was announced that this support would no longer be maintained,&lt;p&gt;Eg. some teams don&amp;#x27;t want their development to happen on a framework with no support from the devs that wrote it.</text></comment>