[cam-stitt]

I'm one of the people in that camp. I loved React, and still think it's a fantastic tool. A few things that have made me move on:

- Svelte (https://svelte.dev)

- People thinking Redux is brilliant. It's good, but it's a far too complex system to simply manage state. I'm aware this isn't React, but I have worked on very few React projects that don't have Redux

- Run-time load. Back to Svelte. It's inspired me to remove as much run-time work as possible.

- API complexity. The React API has exploded over the last year or two. Hooks, memo, portals, error boundaries. Most of them are clever solutions, but are only required due to the limitations of React.

[ng12]

I though svelte was interesting until I read a recent article where they introduced that `$:` label. It seemed like a very poorly thought out approach to me.

That said, I honestly don't think I'll ever go back to using a framework with templates. My distaste for them has only gotten stronger the more I use React.

> People thinking Redux is brilliant

Redux is good as long as you understand what it's good for and only use it when it buys you something. My default recommendation is to not use a state library until you find you need one.

[cam-stitt]

Having used a bit of Svelte 3, the label is quite easy to understand. On top of that, it's valid JS.

> Redux is good as long as you understand what it's good for and only use it when it buys you something. My default recommendation is to not use a state library until you find you need one.

Agree 100%