Why you Should NOT use Svelte

I do Respect Svelte. Take this video with a grain of salt.

[stuvius]

Re-wrote my React project to Svelte and it was the best decision I ever made. Hardly anything to learn because it’s so self explanatory and simple, especially if you already know other frameworks. The documentation is amazing and everything is blazangly fast

[shawnlee]

Challenging to learn Svelte for a React dev? It is probably the simplest and easiest framework out there. 😅

[NicoHeinrich]

Svelte Kit does have an inbuilt routing system and for me, who had never really used React but only Vanilla JS, it was extremely easy to learn. Well, Svelte has just started and the community is growing fast!

[JackKellerPlus]

Former React developer who’s been writing Svelte for the past two years, I gotta say that Svelte is possibly the easiest thing to pick up. It’s vanilla JS with some superpowers sprinkled all over the top!

[SatoshiCommentorto]

When React has broken you so far that vanilla syntax is "hard to read" and a "major disadvantage" 🤦🏼‍♂

[HONjramiroz]

Learning Svelte is one of the best decisions I've made, just my experience

[everyhandletaken]

You were a bit early for April fools on this one?

[senseicodes]

Svelte is difficult to learn??? really?? lol wow. The community and ecosystem is growing pretty fast and nearly all popular technologies have integrations for sveltekit. Anyway that's your take

[alexlun]

I love react because react and I have something in common and that is we were both mistakes that should've never been born.

[dwighsonPavion]

The community is quite large.. and because svelte attempts to be “just javascript “ with super powers, you should look more into framework agnostic approaches. Which means you don’t actually have to learn the framework to make use of it 😅

[celestinemachuca]

mmm nope, I come from embedded system. Making UI with svelte has been a god send for even really complex data visualization. I havent encounter yet an unsolvable problem, yes the documentation can be tricky but honestly not such a biggie(comming from reading 80s timing docs from chips) and routing is easily availible with svelte-kit.

[MagicGamesRayted]

To anyone reading, I do not recommend this content and channel. YT Content is edited / organised nicely, but what you're saying is past braveville, straight into shitcoin land. The title is a joke, developers can use what they think is best suited for the project at hand. Keep learning my guy

[marcframe]

My rebuttle as an avid svelte user, who works primarly as a react developer.

1. challenging to learn and understand it's concepts
I would argue that react has a MUCH higher skill floor than svelte, your example proves the point - bind:value is a much simpler and less error prone concept than react's equivelant of passing props and callback functions

ex.
const [value, setValue] = useState("")
<input value={value} onChange={(e) => setValue(e.detail.value)}

2. the documentation isn't comprehensive
I can kinda agree with that, however I find that svelte draws a lot more from the native W3, and as such there's not too much to learn beyond just learning HTML, CSS and JS

3. Limited Ecosystem
you don't need the large ecosystem that React has. Most of the things you need are out of the box, animations, routing and more are provided for you


as such you don't need to daisy chain libraries together like react, lending to a smaller bundle size and easier development time.

The only part of the react ecosystem that I miss is things like material ui and other component libraries as they can make prototyping easier

4. sveltejs doesn't have official routing


5. small community
the discord is a great community filled with really helpful people.

additionally, as svelte code is so robust, I find that I don't run into hang ups requiring me to get help

also, the API is very stable since the full release of SvelteKit a few months ago and I haven't run into any major bugs or blockers since then

[DevBishwasBh]

Choosing Svelte to develop webapps in our company is the best decision I have ever made as a developer. Svelte/Kit rocks!

[OriginBullet]

This video has convinced me to learn Svelte. Thanks for the anti-advice. I tried learning React... ..yeah, not happening.

[murphytalk]

None of the arguments bothers me. Using Svelte in my recent project was the best technological decision I have made recently. It helped me deliver a complex yet performant solution to my users. I never want to use bloated frameworks like Angular again.

[Samuftie]

seems like, according to you, the primary reason to reject Svelte is because if you are confused, it's hard to ask for help?

probably you should try to read the documentation **slowly**, from top to bottom. I never understand people who find the documentation rubbish.

[MM-ymkk]

"Asked 5 years, 9 months ago"
Is this your best example?

[mohammedzeglam]

why routing even could be a major disadvantage is there a react router from meta even

[joshuacooks]

Counterpoints:
1. Svelte is one of the easiest to learn and it's syntax is very close to vanilla js / html / css with the exception of a few special tags.
2. It's comprehensive. Svelt is not new, and "many many" developers don't have issue finding answers. don't assume problems you have, are inherent or universal or even common.
3. Svelte has a huge ecosystem, on top of everything svelte specific, it also supports almost all vanilla js libraries with ease, something many frameworks have great difficulty with if they can do at all. you can even tree shake out only the that code used for incredibly small fast builds
4. Svelte does have an official router, it's sveltekit, but it supports most any javascript router.

I wouldn't advise others what to do or not do, unless i understood things a lot better. it was a bit jarring to find out someone could drop in with all wrong assumptions and not challenge them. Major Dunning Kruger effect. 😔