[jankiel]

I was stuck once by abusing `bind:` and other time with global exit transitions + sveltekit routing, but that's about it.

React on the other hand feels like a pot warming up and we're the frogs being boiled alive at this point. You can write some perfectly valid, but naive React code and it's going to have some footguns. We're so used to write idiomatic React code we don't even notice that anymore. You learn to use stable references in callback functions, to be careful using Context, and so on. But the list is not short, and it only grows.

Wanna write some naive code in svelte two days in? There's a good chance it's the same code you'd write a year later. Maybe that's what people mean by "just JS".

[benmccann]

> global exit transitions

you'll be happy to know that those are no longer the default in Svelte 4!

[Capricorn2481]

> You learn to use stable references in callback functions, to be careful using Context, and so on. But the list is not short, and it only grows.

It doesn't though. React adds new features that are optional and everyone goes "Pfft, I'm moving to Vue because they added [blank]" I've got old React projects that still work fine.

There are languages/frameworks that move fast and break things and then there are languages that just move fast. And Javascript itself is also very backwards compatible. You could still just be using class components and Redux and be fine. I have no interest in these server components right now.

[re5i5tor]

Love that frog analogy.