[CSMastermind]

I really love the principles that Svelte tries to advance but I find some of their design decisions downright puzzling.

About 2 years ago I had to make a decision about what framework we were going to use for a new project and one of our developers was really into Svelte. I went through the tutorial and made a sample site. It felt like there were always sharp edges I was catching myself on.

I don't remember the specific but I feel like state management got confusing and you had to use work arounds to manually trigger updates in certain situations. Just seemed odd.

[mglikesbikes]

Svelte 5 reimagines the reactivity features (“runes”) and gets rid of the foot-guns, I know exactly what you’re referring to with state management. V5 is much more straightforward to both reason about and bug fix.

[NetOpWibby]

To echo mglikesbikes, I remember wracking my brain trying to figure out state stuff for more involved things like session management at the time. Svelte 5 was released recently and changed how they were doing state.

For me it's annoying because I got used to the old way. For newcomers, it may make more sense by default.

To Svelte's credit, they don't allow you to mix old and new ways of doing state so that's a great way to force people to learn the (new) correct way of doing things. A lot of React's issues are the abundance of old tutorials on the 'net, confusing newcomers trying to do something.