|
|
|
|
|
by balfirevic
3288 days ago
|
|
No, in Vue.js it really doesn't have any drastic effect - or almost any effect on what you would call "architecture".
I have to ask - are you just talking abstractly about two way data binding or specifically as implemented in Vue.js? |
|
The reason is that "effects", "data modifications", or whatever you want to call them are now local and appear everywhere. As your application grows it becomes harder and harder to know where and how your data model is updated.
This becomes especially apparent as you introduce more complicated workflows where you can't update a single value of state at a time but instead would like to treat it as a transaction.
It can also appear when dealing with computed/derived state.
Two-way data binding is fine for a simple form of 5 values. But once you start trying to build a larger application the desire for a top-down data flow and isolated state modifications becomes very apparent.
It's not an attack on Vue.js, as you have options like veux. I'm merely stating that there are very large disadvantages to two-way databinding itself.