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

181–190 of 289 posts

Re: Migrating from Vue 2 to Svelte

#181

Post by hardwaresofton »

zztop44 wrote: post #125
hardwaresofton wrote: post #73

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 check…

Same. I normally prefer boring old tech, but I’ve migrated all my projects over to Sveltekit. Yep, breaking changes are annoying but it’s worth it. It’s got the point where you’d need to pay me lot to work on a Vue or (especially) React project.

Yeah I look at it this way:

- Angular introduces structure, people realize that Directives are awesome but dirty checking is bad.

- React re-focused frontend on components (to be fair Backbone/Marionette and some MVVM stuff was going this way already but whatever), people realize they really mostly just want big hierarchies of components and to minimize everything else. The Flux data flow pattern is alluring too but kind of unnecessary.

- Vue cloned react but improved on it by introducing the data object via automatic tracking and radically simpler APIs. I read up and was productive with Vue in like... 1 day of reading docs.

- Svelte builds on all of that, moves more magic into the compiler and introduces weird syntax but thoroughly consistent ergonomics and lower complexity.

- Everyone goes SSR

For people who want jobs, React is still king and probably will be for a very very long time. But you can pry SvelteKit from my cold dead hands.

Re: Migrating from Vue 2 to Svelte

#182

Post by KyeRussell »

_s_a_m_ wrote: post #128
fenomas wrote: post #34

Some months ago I did the same thing as TFA - took a look at Vue3 and decided to change my main project's UI from Vue2 to svelte. So far I've been really happy with it. In my case the big motivator was that with Vue, whenever I worked on my UI code I found I spent most of my time thinking about Vue and not about the UI. I think the key issue was that Vue seems to offer several different abstractions for each of the t…

I find your points rather weird. > e.g. how to make a piece of state inside one component accessible from another. That is logically the same with every component framework, there is only one correct way to design it, flowing inside data are props, outgoing data are events. Was always the same. > Then when I saw Vue3 was adding a new, apparently separate way of > doing things (the composition API), but also not depre…

I’m kinda confused by this and your other replies in this thread. You seem to be defending Vue, specifically Vue 2, in almost a drive by fashion. You don’t seem to be considering any of the points actually being made. No bystander is interested in hearing the drive by argument of someone without an open mind.

Re: Migrating from Vue 2 to Svelte

#183

Post by caseymarquis »

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…

I migrated from vue 2 about 4 months ago seeking better typescript support and looking to move away from webpack. While I absolutely loved the simplicity and feel of svelte, I came to the same conclusion that it is not ready for a major production application yet. In a few years, I'm hoping vue setup scripts are as low friction as svelte or it may be time to switch over (they're close now, if you're using the latest macros, which may or may not be in beta still).

Re: Migrating from Vue 2 to Svelte

#184

Post by DrScientist »

Reading this thread I'm struck by how it's all about moving from this to that, or I use this framework because of these great components only available in X.

Isn't the problem that most of these frameworks or components result in an either/or choice and fragmentation?

Re: Migrating from Vue 2 to Svelte

#185

Post by [deleted] »

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…

[deleted]

Re: Migrating from Vue 2 to Svelte

#186

Post by igtztorrero »

I never like Vue2 extra verbose code, when I meet Svelte, I think: "This is it, just want I need" then realized Vue3 is an intended effort of Evan You (creator of Vue) to look like Svelte, I start to use Vue3 because all frameworks and libraries that exists in Vue, actually using Quasar ( excellent and full framework to use Vue2 and Vue3 )

I don't know if Svelte will ever get the same punch of Vue Libraries and frameworks that exists now.

Let see what happens.

Meanwhile I stayed with Vue3

Cheers!!!

Re: Migrating from Vue 2 to Svelte

#187

Post by KyeRussell »

mozey wrote: post #86
nlnn wrote: post #77

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 - incu…

As a backend person that used to be a front end person, there has never been a better time for using VanillaJS (or TypeScript), HTML, and CSS? > someday pick one to learn in depth without worrying about it being replaced by the next hotness So maybe the trick is to not use a framework. Like, I don't need a "framework" for backend dev, just a toolbox of good libraries. The tooling around TypeScript is similar to a bac…

If you’re working on a reasonably sized project “without a framework”, and haven’t effectively built your own, I’m very skeptical of the engineering practices at play.

Re: Migrating from Vue 2 to Svelte

#188

Post by KyeRussell »

b112 wrote: post #87
nlnn wrote: post #77

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 - incu…

I keep hoping things will settle a bit more so that I can someday pick one You are in the wrong industry, to think this will happen any time soon. Change has been fast in computing, for decades. Stand still, and you are overrun and eventually your knowledge moves towards irrelevance. Doctors need to keep up to date with new medical information, new drugs, new warnings about drugs, new techniques. Lawyers need to read…

This is a common rebuttal against any dissent against the insane flux of the front end space and I genuinely don’t believe that anyone with significant experience in software actually believes it.

The front end space is really quite unique in its fragmentation and pace of change. Things are…maybe starting to cool down a touch, but not really. We can talk til the cows come home about how this or that have caused things to be how they are, but simply chalking this up to “things change fast in tech” - beyond just being a thought-terminating ‘shrug your shoulders’ platitude that I’d probably hear from a non-tech family member over Christmas lunch - is really missing most of what’s going on here.

Re: Migrating from Vue 2 to Svelte

#189

Post by sph »

tr1ll10nb1ll wrote: post #138
Majestic121 wrote: post #109

Earlier quoted context omitted.

React is not really a new hotness anymore though.

Imo, makes it the best bet for building anything. There's still a new JS framework everyday but if you ignore all that noise and for production-quality software just have a look at React and the most popular meta framework on it, Next.js, you'll be more than alright.

Next.js is not a good general purpose React framework. It is good for static sites with sparse dynamic pages but nothing more complex. And the documentation is still woefully inadequate.

Don't be like me, choosing to build an entire app on Next.js and hating every moment of it after the honeymoon period ended 2 weeks in. Live and learn.

Re: Migrating from Vue 2 to Svelte

#190

Post by mozey »

KyeRussell wrote: post #187
mozey wrote: post #86

Earlier quoted context omitted.

As a backend person that used to be a front end person, there has never been a better time for using VanillaJS (or TypeScript), HTML, and CSS? > someday pick one to learn in depth without worrying about it being replaced by the next hotness So maybe the trick is to not use a framework. Like, I don't need a "framework" for backend dev, just a toolbox of good libraries. The tooling around TypeScript is similar to a bac…

If you’re working on a reasonably sized project “without a framework”, and haven’t effectively built your own, I’m very skeptical of the engineering practices at play.

Not using a framework doesn't automatically imply everything is built from scratch. Maybe I prefer calling libraries, instead of plugging my code into a framework. I could also implement patterns using the batteries included features of the platform. For example Web Components on the frontend, or a REST API on the backend built using the standard Go "net/http" package
Post reply on HN