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
0
0
42
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.
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.

8:46 PM Β· Oct 23, 2021

1
0
0
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
0
0
4
Good example from a recent article: People who embrace modern computing paradigms, or learned computers in the last 10 years, don’t understand directories. Why bother organizing your stuff when search is the fastest way to access information anyway? theverge.com/22684730/studen…
0
3
1
7