Legit question: What makes Svelte's 2-way binding better than its 2-way binding predecessors? Remember, part of the success of React is the rejection of 2-way binding and the bugs/confusion that came w/ it, favoring one-way data flow. The verbosity is a feature, not a bug.
Real quick! I was discussing this with @catalinmpit and thought I'd share! Same component, does the same thing. First image React the next one is Svelte. This was one of the big "aha!" moments for me coming from React. Take a look at the code in the next tweet!
Show this thread
13
13
1
160
I won't deny the verbosity can get old. I'm also not insulting Svelte in any way. I genuinely want to understand how we've gone full circle on 2-way binding, and what makes it better in Svelte than previous 2-way binding frameworks.
6
42
Replying to @kyleshevlin
5+ years have passed. You have a whole generation of programmers who have never felt the pain that React solves and don’t understand why it exists.

Oct 23, 2021 · 8:45 PM UTC

3
3
2
38
Replying to @Swizec @kyleshevlin
👀👀👀 heh. seriously, this is half the reason why I had to go rewrite the Redux docs tutorials :) no one today knows that "Flux" was, why 1WDF with "dispatched actions" was better than Backbone models cascading events, etc.
1
9
I worry about this when teaching. Every day feels like I am less able to understand the perspective of newcomers. So much advice makes no sense in a modern context
2
4
Replying to @Swizec @kyleshevlin
That always baffles me. I got into programming a few years back, and I am always in the dilemma of whether to dig deep into abstractions or not.
Replying to @Swizec @kyleshevlin
I was this a year ago, but now fell in love with Next.js. I don’t learn quickly, but I do learn 😅