Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating from Vue 2 to Svelte

escape.tech

Post reply on HN
Print view View original

71–80 of 289 posts

Re: Migrating from Vue 2 to Svelte

#71

Post by Semaphor »

trinovantes wrote: post #61
Semaphor wrote: post #14

Earlier quoted context omitted.

edit: Disregard, this is wrong. ----- I agree with the rest, but how do you use imported TS enums in your template? Something like this being impossible is regularly a pain point for me: slotProps.data.type === ArticleTypes.SomeType

`ArticleTypes` should be automatically available in the template just from importing it if you use script setup Otherwise you also need to return it in the setup function (composition) or store a local copy of it in the data field (options)

It… does. Now I wonder if this was not in 3 from the beginning, or if I simply always assumed this behavior was the same after upgrading from Vue2. Wow. Thanks.

Re: Migrating from Vue 2 to Svelte

#72

Post by dmitriid »

Abishek_Muthian wrote: post #64

JavaScript framework fence sitters who are planning to use Svelte for a component in your SSR application please note that that their Web Components support is very buggy and Svelte team has no intention to fix it, Because(In their own words)[1] - "Nobody on the core maintainers team is particularly fond of Web Components" Yet,Their official doc includes support for Custom Elements; I found that svelte is not the rig…

> planning to use Svelte for a component in your SSR application please note that that their Web Components support

No idea why you put SSR and web components in the same sentence, and in a way that presumes that web components are required for that, or at all.

1. web components are literally incompatible with SSR and all SSR solutions for them are ugly hacks.

2. It's not just personal "fondness" that prevents Svelte from doing more about web components. There are multiple documented downsides, including by Rich Harris, the author of Svelte

3. As long as you pretend you need web components for SSR, no framework will be right for you, including web components themselves. Meanwhile every single framework is several light years ahead of anything web-component-related for SSR. Especially Svelte whose authors and contributors have thought really hard about SSR.

Re: Migrating from Vue 2 to Svelte

#73

Post by hardwaresofton »

Svelte & SvelteKit has been wonderfully productive for me. It's a bit insane that I have adopted it across so many projects of mine despite the fact it is pre 1.0 (well that has more to do with me I guess), but I am just faster with it.

I have used a lot of frontend frameworks over the years, and before SvelteKit Vue & Nuxt were what I was warming up to.

The article really focused on measurable things like type checking and surveys (not sure exactly how much that's relevant to a single team), but if I tried to quantify:

- Svelte/Kit is conceptually small - Svelte/Kit's diversions from common practice are disruptive at first but quite productive if you really let them sink in (ex. path based naming, +page.svelte/+page.server.ts/+server.ts) - Svelte's ability to run in various different modes (SSR/node/vercel/etc) is awesome

At this point Vue3 & Nuxt3, Remix, etc have caught up in many ways but I really really love using Svelte/SvelteKit. I recommend trying it at least once.

Re: Migrating from Vue 2 to Svelte

#74

Post by kristiandupont »

for1nner wrote: post #50

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 "someone on the dev team advocated and fluffed enough figures to convince us. So now we're going to tell you why it was the right choice!" I say all this pretty confidently as someone currently maintaining a massive legacy vue2 app…

Yeah, "We didn't consider React because it would have taken too much time to learn" doesn't sound very convincing to me.

Re: Migrating from Vue 2 to Svelte

#77

Post by nlnn »

As a primarily backend person, it's always interesting to read about this sort of thing as an outsider with little appreciation for the nuances/challenges people face using these frameworks.

I keep hoping things will settle a bit more so that I can someday pick one to learn in depth without worrying about it being replaced by the next hotness.

Am I right in thinking the state of major players is roughly:

React - incumbent, slow, vast, but widely used Vue - main challenger to React, aimed to fix many issues, but 2->3 migration tricky Svelte - lighter compiled alternative for smaller projects, faster, but more niche Solid - even faster, more similar to React, but too new/small for bigger projects

Re: Migrating from Vue 2 to Svelte

#78

Post by randomsearch »

for1nner wrote: post #50

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 "someone on the dev team advocated and fluffed enough figures to convince us. So now we're going to tell you why it was the right choice!" I say all this pretty confidently as someone currently maintaining a massive legacy vue2 app…

In what way is being on Vue 2 painful? Using it in production, zero problems, everyone understands it, does everything we need.

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.

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.

Did take a look at Svelte, agree with you.

Re: Migrating from Vue 2 to Svelte

#79

Post by the_gipsy »

sli wrote: post #32

Articles like this make me wish Elm was still under active development to smooth out its pain points and also not so weirdly hostile towards forks.

You can still use Elm of course. It just has the exact opposite energy as todays.js hottest framework.
Post reply on HN