3 ms·
> In a function component, we need to think about what values stay in-sync. So we are removing Classes in favor of Functions. Something tells me that on the n
by c-smile 7y ago
> In a function component, we need to think about what values stay in-sync.
So we are removing Classes in favor of Functions.
Something tells me that on the next iteration we will see something like this:
"In a declarative component, we just need to declare what UI elements shall stay in-sync with what items in data model."
And that is precisely what Angular is based on (declarative two way binding).
And the cycle of evolution spiral will be complete.
Life goes on ...
- gombosg 7y agoWhy? This is just slippery slope arguing. Two-way bound data is a huge leap in framework complexity. They require Zone.js stuff in Angular and use of ES2015 Proxies in Vue.js. React has neither of these. Hooks is basically a different syntax describing the same framework. I personally love them since I no longer need to care about lifecycle methods, but can describe state and state change logic.
- imtringued 7y agoTwo way binding is absolutely awful and what React hooks appear to do is one way data binding which has always been considered superior. Of course one way data binding isn't exactly new but your comment is making some fundamental mistakes.