@@webdevladder I have worked with complex states in both Svelte and React. And can't say React's reactivity was easy to work with ever people hate useEffect for a reason after all. Even with Sveltes reactivity quirks I never found my self debuging as much as I did in React land.
I went from angular (hated it but was v2 then 4), then did React wow what a huge improvement, just didn't like what seemed to be like component slides more from needing to deal with context... Then found Svelte 3, and absolutely loved it, felt simple, direct and just right... Stepped away from Svelete for a bit to focus on work, getting back into Svelte i'm going from 3 to 5. Did a bit of a detour looking at Solid JS. But back to Svelte 5. My only question might be what else was missed. But that said, might feel like enough svelte has been written by enough people most if not all the edge cases have been caught an dealt with now... To their credit sure seem the Svelte team did a great job maintaining compatibility from what i see and only changed stuff that had to in order to fix bad side effects/behaviors...
I don't complain about the changes but I would love to have a better syntax sugar that hides this complexity from the user. If you have a compilation step why not use it?
there was one weird situation where I just couldn't make it reactive, finally I've put awaited 1ms timeout in and... it worked but that clearly shouldn't be like that, I wonder if runes will fix that
interesting yeah my guess would be yes, runes are synchronously consistent so you shouldn't need timeouts to see reactive updates - I'd be happy to look at a REPL if you want
@@webdevladder I basically finished updating my project, there's only that timeout left, I'll remove it and see what happens there's a big chance I just did something wrong, I'm a backend dev creating imperative code basically half my life so the reactivity is still like a black magic for me, but there are times when you have to use unfamiliar tools to get things done, Svelte(Kit) looked much less intimidating than React, Angular or Vue, and as I needed some JS libs on the backend and some SPA-ish action on the frontend Laravel with Livewire wouldn't work that nicely overall I'm pretty happy with the experience, both of Svelte 4 and 5
And somehow svelte 3/4 reactivity is still better than reacts and easier to reason about
I agree in the simplest cases, but not beyond them, and that's where most difficulty and bugs appear.
@@webdevladder I have worked with complex states in both Svelte and React.
And can't say React's reactivity was easy to work with ever people hate useEffect for a reason after all.
Even with Sveltes reactivity quirks I never found my self debuging as much as I did in React land.
React reactivity is hard! And compared to svelte 3/4 at least correct ans consistent which is mote i😂
I went from angular (hated it but was v2 then 4), then did React wow what a huge improvement, just didn't like what seemed to be like component slides more from needing to deal with context... Then found Svelte 3, and absolutely loved it, felt simple, direct and just right... Stepped away from Svelete for a bit to focus on work, getting back into Svelte i'm going from 3 to 5. Did a bit of a detour looking at Solid JS. But back to Svelte 5. My only question might be what else was missed. But that said, might feel like enough svelte has been written by enough people most if not all the edge cases have been caught an dealt with now... To their credit sure seem the Svelte team did a great job maintaining compatibility from what i see and only changed stuff that had to in order to fix bad side effects/behaviors...
Very insightful... 👍
svelte is the future
Thanks!!
I don't complain about the changes but I would love to have a better syntax sugar that hides this complexity from the user. If you have a compilation step why not use it?
What "complexity"?
learn to code
@@ivan.jeremic if everybody thinks like you we were still coding in assembly.
there was one weird situation where I just couldn't make it reactive, finally I've put awaited 1ms timeout in and... it worked
but that clearly shouldn't be like that, I wonder if runes will fix that
interesting yeah my guess would be yes, runes are synchronously consistent so you shouldn't need timeouts to see reactive updates - I'd be happy to look at a REPL if you want
@@webdevladder I basically finished updating my project, there's only that timeout left, I'll remove it and see what happens
there's a big chance I just did something wrong, I'm a backend dev creating imperative code basically half my life so the reactivity is still like a black magic for me, but there are times when you have to use unfamiliar tools to get things done, Svelte(Kit) looked much less intimidating than React, Angular or Vue, and as I needed some JS libs on the backend and some SPA-ish action on the frontend Laravel with Livewire wouldn't work that nicely
overall I'm pretty happy with the experience, both of Svelte 4 and 5
hopefully react will use a compiler and we're not going to have to deal with the poor svelte ecosystem just for the sake of performance.
Just write better React code
What poor ecosystem? You mean you are mad you didnt spend 3 hours choosing a state manager because it is built in?
"Poor ecosystem", lol. Pretty much any vanilla JS NPM package works out of the box with Svelte. You don't need Svelte wrappers to make it work.
svelte uses JS ecosystem lmao.