Any advantage of using Svelte instead of React or Vue?
_janc_June 18, 2026 at 2:20 PM
Is it just because of performance?
DeltaLaboratoryJune 18, 2026 at 2:35 PM
Virtually everything except job market
Intrepid-Ordinary699June 18, 2026 at 11:32 PM
I might get downvoted for saying this, but I think the job market is equally challenging nowadays regardless of the library or framework, and this is becoming an old discussion.
Indeed, AI is helping companies change their tech stacks and the adoption of SvelteKit is increasing. Trust me bro!
Shoddy_One4465June 22, 2026 at 6:17 PM
Svelte costs less tokens. Seriously!
I developed a complex website 3x using Svelte, React and Vue using Claude 4.8
Svelte was much cheaper.
Just like elixir is cheaper than Python
Zig is cheaper than rust
Elixir development is cheaper than most languages.
Does it really matter anymore what the language is? It’s all about speed and token cost not man days.
It’s: How fast you can achieve a bug free solution using the minimum number of tokens.
The technologies that are cheapest to develop with LLMs should prevail unless the token vendors can influence the technology stacks.
But, hey we’ve been driving gasoline cars for hundreds years - which is proof that when it comes to technology the markets are never efficient.
97689456489564June 19, 2026 at 3:46 PM
For what it's worth, AI is what made me start "using" Svelte for the first time. I couldn't justify it before, despite researching and concluding it is overall likely the best framework, but now that I can basically rewrite anything in anything, I went from never touching Svelte to using it everywhere. Agents seem to work well with it.
I have never actually written a line of Svelte code myself - or, frankly, any frontend code, pre-AI I've always just worked with messy vanilla JS/TS behemoths - but I basically just batter the AIs with "okay try to split this into more components and re-use these existing components instead of re-inventing new components just for this" every so often and the end result seems decent enough
Upstairs_Toe_3560June 19, 2026 at 11:49 PM
very clear comment
Eugen_IvanovicJune 22, 2026 at 9:50 PM
Oh man. Slam dunk comment.
HansVonMansJune 19, 2026 at 12:29 PM
Hahaha oh lord imagine optimizing for hireability for hand-coding jobs in 2026
RedlineQuokkaJune 20, 2026 at 12:18 AM
While not hand-coding, the job openings still require experience in the specific language and framework and infra the project is using, not just in some language, framework, and infra.
Cause you still need to be able to tell where the output makes sense amd where it doesn't
LinkPlay9June 18, 2026 at 2:29 PM
its just nicer to work with imo. vue is similar, but the difference between react is staggering. react forces you to learn a bunch of extra concepts and loopholes and footguns to avoid.
sorainyuserJune 18, 2026 at 3:10 PM
Sadly I converted from sveltekit to nuxt because it is just big enough to don’t worry about scaling your team on it. Svelte is great, but lacking for me to take it as a choice for building a software house company
LinkPlay9June 18, 2026 at 3:58 PM
whats lacking exactly? whats stopping a team using svelte from scaling?
sorainyuserJune 18, 2026 at 5:05 PM
It can serve the same purposes as vue or react project. I even started my company using svelte, and it's possible.
Svelte can be faster in development, but at the same time when you encounter problem it's so much harder to resolve. Not talking about talent aquisition as it's so much simpler for vue, as there are just more devs for it.
I love svelte and was always an advocate, don't take me wrong.
But when you're scaling business you want to focus on marketing and selling side, not on tech.
nullbyte420June 18, 2026 at 5:18 PM
Why is it harder to resolve Svelte problems? The codebase is pretty well maintained by some clearly very competent people, so it's possible to take a look at why it doesn't work. Especially with AI assistance. And the documentation is pretty great too.
To me, the most confusing thing about sveltekit is how simple it is. It's like I expect more black magic than there is.
But maybe I haven't used it long enough. What kind of issues are you thinking of?
kevin_whitleyJune 18, 2026 at 5:32 PM
It's just not (in my experience).
I've been building in Svelte since the early days, with many apps in production. I build in React for the normal job, and Svelte for all my own stuff.
React creates an interesting paradox where it ***introduces*** many issues due to the complexity it requires.
This makes developers fear a smaller audience in Svelte because they wonder *"who would answer all these questions I always have???"* But the answer is closer to *"many of these questions you would not even have in Svelte"*.
This is also why I maintain that any dev smart enough to hold their own in React can absolutely crush it (in no time) in Svelte.
nullbyte420June 18, 2026 at 5:42 PM
Yeah agreed, that's exactly what I mean. The scariest thing is that there's not a lot to worry about in Svelte so it looks like something is missing
SaabiMeisterJune 18, 2026 at 10:11 PM
The worst issues I've had to deal with using Svelte were the subtle differences in how chains of derived store dependencies and reactive `$:` statements handled updates, creating differences in behaviour to apparently equivalent logic.
But even that was predictable, architecturally understandable, easy to work with and so hardly ever a significant issue that most experienced Svelte devs are not even aware of this.
And then runes came into the picture, which are much closer t9 stores semantically and the issue is even less significant.
kevin_whitleyJune 18, 2026 at 10:40 PM
I feel like i'm one of the few that don't actually love runes... they're awesome in some cases, and feel like a DX regression in others.
Totally agree w you on some of the reactivity challenges, but then every reactive framework seems to have that issue in some way or another (certainly in React in my experience). That said, I feel like I write less code and it's far more human-readable than the hook-soup necessities in React!
SaabiMeisterJune 18, 2026 at 10:43 PM
Absolutely
OhByGolly_June 18, 2026 at 5:01 PM
Nothing outside of it being relatively green for new devs.
kevin_whitleyJune 18, 2026 at 5:27 PM
I'd argue that any dev smart enough to grasp React can be outperforming their React-self in Svelte within a week or so.
They'll of course still have some fumbling through "how do you do X in Svelte" translations, but even with the docs permanently open, they can typically out-pace their React hook-soup self.
BTolputtJune 18, 2026 at 2:25 PM
Easier to integrate "raw" JavaScript libraries because Svelte acts on real DOM objects, not virtual ones. This is why I continue to use it, the performance advantage is just a bonus to me.
hyrumwhiteJune 18, 2026 at 9:40 PM
For Vue at least, a vanilla JS library is a composable an away from integration. Vue uses the virtual domain for diffing, but it updates the dom on setup, and subsequent updates only occur atomically after state changes.
React gets dicier with rerenders.
ryutaromackJune 19, 2026 at 5:14 AM
I agree. I've run into a few times where I needed to integrate vanilla javascript libraries and it just works with svelte.
I haven't used vue in ages so don't know or remember if it has similar capabilities.
therealPaulPlayJune 18, 2026 at 2:28 PM
No need to ship a runtime since Svelte doesn’t use a virtual dom.
Jona-AndersJune 18, 2026 at 3:28 PM
Svelte has a runtime with svelte 5 for runes and signals - but it is small and enables applications to scale much better in size than before. So before svelte 5 there was no runtime, but therefore code was "duplicated" between components. Now it is a bit bigger to start with, but therefor the application grows a lot slower than before. So for most purposes applications are now smaller than before.
EvilsushioneJune 19, 2026 at 12:33 AM
I thought it uses JavaScript signals underneath.
Jona-AndersJune 19, 2026 at 2:23 AM
Sure, signals are implemented in JavaScript, but there is no standard for signals in JavaScript. I think there was a proposal for one a while ago, but it is not a standard yet.
Subject_Health_3182June 18, 2026 at 3:32 PM
DX.
I studied React for like 3 times, different courses, dozens of pet projects. It took me about 4 months before it clicked.
But with Svelte I was ready to create within 3 days of studying.
BTW it's ridiculous that Svelte feels closer to Vanilla JS, than React. Even though it's DSL.
kevin_whitleyJune 18, 2026 at 5:34 PM
My experience as well. Quite a few years of React building under my belt before I touched Svelte, and I within a day or two I was already faster at the latter.
Even just going through the tutorials back then was one mind-blown reaction after another... thinking "omg, this would have taken so much more in React (or it just isn't even natively handled)".
hyrumwhiteJune 18, 2026 at 9:45 PM
React has a dsl too, JSX is not vanilla
Subject_Health_3182June 18, 2026 at 10:06 PM
JSX is synthetic sugar for React.createElement()
hyrumwhiteJune 19, 2026 at 12:00 AM
Yeah, it is syntactic sugar.
Vue templates are sugar for Vue createElement
Svelte templates are sugar for dom operations
They each use non standard file extensions, .tsx/jsx, .vue and .svelte.
All are DSLs that are not compatible with vanilla JS
Subject_Health_3182June 19, 2026 at 12:08 AM
hmm, makes sense
srlechugaJune 18, 2026 at 3:44 PM
Mental health
demian_westJune 18, 2026 at 3:13 PM
Clearer and simpler code, less footguns and framework idiosyncrasies, no vDOM (it goes beyond performance).
BTW, there are a growing number of high-performing big players (not enough) that have gone full on Svelte (Apple, Hugging face,...).
Rheath72June 18, 2026 at 4:59 PM
Been writing React professionally since it was a niche new library from Facebook. Svelte is better in every way.
kevin_whitleyJune 18, 2026 at 5:36 PM
Same team on both accounts! Still work in React to this day (for work), and can still safely say Svelte is just cleaner, simpler, better performance, and solves so many app-level issues that React does not.
Rheath72June 18, 2026 at 5:00 PM
Actually linting tools are better for React still.
IamNochaoJune 18, 2026 at 2:26 PM
Granular reactivity?
kakarlusJune 18, 2026 at 2:32 PM
Less stress
Several_Bumblebee153June 18, 2026 at 2:32 PM
for agentic coding less token expediture
demian_westJune 18, 2026 at 3:09 PM
Ah, lol, I didn't though about this one
Sea_Chipmunk5395June 18, 2026 at 10:25 PM
Wrong until you prove it
snooketteJune 18, 2026 at 10:59 PM
Haven’t tried recently but i felt the opposite a few months back as dumb models just installed react packages even though I told it not to.
jessycormierJune 18, 2026 at 2:32 PM
I found it easy to use when creating an image generator library with a .png route this just isn't some to you can do in vue. You can in react since it supports those server side functions. Svelte felt easier and cleaner when I tested both. (Used for generating unique headers for posts on a blog based on a slug version of the title as the seed)
egehancryJune 18, 2026 at 7:54 PM
Svelte simply revolutionized front-end development.
Front-end is two things.
1. You declare what your HTML/CSS is for a given set of variables (state): that's templating.
2. You write the logic connecting user actions to changes in that state: that's programming.
That's the whole job.
Svelte 5 took both and perfected them.
Programming: with runes, a state is just a TypeScript variable. `let count = $state(0)`, then `count++`. You change a variable by changing it. Nothing special, pure TypeScript.
Templating: you make a `.svelte` file and write HTML/CSS with a great templating language, by using those state variables you wrote in pure TypeScript. It's perfect.
Now React.
Programming: a state isn't a variable, it's a hook. `const [count, setCount] = useState(0)`. You have to go through `setCount`. You don't change a regular TypeScript variable. You ask React to change it for you via API.
Templating: a component is a function, and the template is whatever that function returns.
But look at where the template lives: inside the function. `useState` only works inside that same function. So your state and your template are forced to live in the exact same place, one inseparable block. You can't put your state in one file and your template in another. React welds them together by design.
Svelte doesn't. Your state can live in its own `.svelte.ts` file, with its own in pure TypeScript logic. Your template (`.svelte` file) can import whatever states it needs from `.svelte.ts` files, and connect buttons to the necessary logic.
These are just some things off the top of my head, and this is only the frontend side. SvelteKit is also revolutionary in its own for full-stack.
Own-Phone2375June 18, 2026 at 4:14 PM
clean syntax, almost same like vue,
not too much need ext deps
HeraldiqueJune 18, 2026 at 5:15 PM
It’s good for embedded web development cause it uses less storage
ijustwrotesomecssJune 18, 2026 at 9:16 PM
Angular for the streets, Svelte for the sheets
Electronic-Pie-1879June 24, 2026 at 3:07 PM
Developer Experiance is just waaaay nicer, worked for 3 years in a Svelte, SvelteKit, Typescript, GraphQL stack. It was a bless. Miss those days.
_janc_June 24, 2026 at 5:27 PM
Can you elaborate a bit by nicer?
Electronic-Pie-1879June 25, 2026 at 6:47 PM
React often feels like you need a whole list of dependencies just to get basic things working. A lot of it can feel hacky, not very rounded, and full of weird concepts or hidden pitfalls that are not obvious at first. Over time, it feels bloated, especially in complex components like a checkout / payment or similar things.
I worked on an online shop for a fashion label here in Germany, where we replatformed from a PHP, Smarty, and Vue stack to a full rewrite with Svelte, SvelteKit, TypeScript, and GraphQL. After years of working with that legacy codebase, it was honestly refreshing to see a different approach. I was hooked on Svelte pretty quickly. It was fun to work with, and because I enjoyed it so much, I learned a lot along the way in General and even did things as Frontend Developer i would tought i never touch like writing NestJS Services we also had which was running in the background.
I got so into it that I basically led the migration from Svelte 4 to Svelte 5. I explained runes and the other major new concepts to the team, since that version changed quite a few things.
What I like about Svelte is that it feels idiomatic, simple, and straightforward with minimal code. You do not constantly have to fight the framework or think through layers of side effects. Most of the time, you just write the code and it works the way you expect.
Even today all my private projects are built with Svelte, SvelteKit, and TypeScript.
If you are curious, try the tutorial on https://svelte.dev/tutorial/svelte/welcome-to-svelte It shows pretty quickly how easy and convenient the framework is to use. :)
moobnaster6969June 18, 2026 at 4:35 PM
Remote functions: https://svelte.dev/docs/kit/remote-functions
FluxKrakenJune 18, 2026 at 5:49 PM
And now they support real time streaming.
lastWallEJune 18, 2026 at 9:59 PM
You keep your sanity?
KaiAusBerlinJune 18, 2026 at 5:11 PM
Any? 😂 Made my day
Spare_Message_3607June 18, 2026 at 6:24 PM
it is hard to write bad code. the compiler just does the heavy lifting. A production dashboard was 2MB on my React MVP to 500kb in mt Svelte Code. Everything loads fast, the app is snappy, code is not callback hell. Less compromised package ecosystem, less libraries to learn. it just works.
wentalloutJune 18, 2026 at 7:00 PM
1. DX
2. Prob save more tokens for agentic coding
3. No strange concepts to learn... unlike React
TheRealSkytheJune 18, 2026 at 8:13 PM
underwatercr312June 18, 2026 at 10:06 PM
Everything
ffiwJune 19, 2026 at 8:28 AM
Easier on the coding agents. They can reason easier with svelte as things aren't too abstracted away.
SseyhJune 19, 2026 at 11:22 AM
You'll love it. Thats the biggest advantage.
HarinderpreetJune 19, 2026 at 3:49 PM
One library for Frontend and Backend, React can do too, however Reac makes it complicated.
Clean Code, Less code
SAF1NJune 19, 2026 at 9:26 PM
react: we have solutions to your problems, and then we have solutions to the problems that our previous solutions made... and now you're downloading 600kb worth of react on page load
svelte: we got reactivity... state management... and JavaScript, figure out the solution to your problem by yourself bro
nhoyjoyJune 20, 2026 at 10:57 AM
The pivot would be Web Components, and smart use of bundling. We don't need to fully rely on a full set framework. Pick whatever that works for small scope, build components/widget and wrap the context so that AI can better delivery, and you can control the quality as well. But this doesn't matter since we want to make everything proprietary with Rust/Go and Web Assembly.
venir_devJune 20, 2026 at 10:57 PM
I'd say the question is "vs react". so, developer experience.
Vue has a pretty much identical DX.
tardoosJune 18, 2026 at 3:30 PM
Yes, you will have fun debugging when they ship a completely broken version of the framework
Other than that, DX is much, much worse. TS integration is also much worse. Svelte is a fun framework if you use it on your to-do list type of project.
TwystedLyfeJune 18, 2026 at 3:36 PM
Software has bugs, they fixed it already. Get over it.
Exact-Big3505June 18, 2026 at 3:59 PM
mehhhhh they released a fixed version in 24 hours. You shouldn't be installing packages that young anyway in this day and age courtesy of supply chain attacks.
tardoosJune 18, 2026 at 7:23 PM
>mehhhhh they released a fixed version in 24 hours
They did?
https://www.npmjs.com/package/svelte?activeTab=versions
I thought the broken version was the one that was the latest for 3 days with 130k downloads.
FluxKrakenJune 18, 2026 at 5:50 PM
You update to the newest verions of all your packages, in production? Are you begging to be hacked? No minimum age policy? At all?
Alternative_Web7202June 18, 2026 at 6:10 PM
You'd better quit drinking
imavlastimovJune 19, 2026 at 10:00 AM
Just use that what AI is best at.