I feel like you are looking at this wrong...
There are two things that matter.
We say everything needs a virtual dom, then we build a website with React that does not need reactivity. Looking at almost every marketing site ever.
So I choose svelte because of the lower bundle size.
Then we say it performs better, the virtual dom. Well, most performance tests I have seen show the opposite. That svelte out performs virtual dom libraries.
For this argument I look too scale. The stress cases have thousands and thousands of things being updated. My web app does not, so this does not seem to matter much.
So once again, back to bundle size, and I choose svelte.
I appreciate the technical argument and the debate. But we all seem to forget that most of the web is Wordpress and jQuery still. That vanilla HTML, CSS and JS solve most of our issues and we are debating developer experience not user experience.
Start with the user experience, you won’t go wrong. But don’t claim performance issues without a actual user context and impact. And don’t sacrifice bundle size for a few extra frames a user can’t decern because you think it’s neat, or want to defend your technology choices.
Svelte performs a lot better when the app is small. Imagine a live updating website or Facebook being developed in svelte.
Bundle size does matter but as the application grows, all the functionalities in it are a need.
Where do you see proof that svelte can’t handle something like Facebook. That is just assumptions. Facebook was built without a virtual dom long before it had one.
Also, once again most websites are not the size of Facebook. So it’s about your needs.
I would also argue it’s about how the developers work offline, the component architecture, that makes these frameworks valuable. Not the user experience. Nothing a SPA, svelte or react, does is something a standard site can’t do from a users point of view.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.