Google Developer Expert | Auth0 Ambassador | Media Developer Expert at Cloudinary | Twilio Champ | Technical Coach at SpringBoard | Google Women Techmaker | Postman Supernova | AWS | Microsoft MVP
Can you explain this line "State in components is (mostly) a bad idea" are you talking the state handle by Ngrx, Vuex or Redux (Angular, Vue, React... respectively) if that's what you mean, can you tell me where did you get that the industry says that state is a bad idea? I have heard than handling the state of the apps with the tools mentioned above is the way to go. I just want to make sure we are talking about the same.
UI Consultant, Maker & Technical Writer.
I write about JS, TS, Rx, Angular & all things Front End
🇮🇹🇬🇧
Follow me on Twitter: https://twitter.com/gc_psk
Founder of https://makerkit.dev
Hi Pato - what I meant by that is that we used to write state entirely in components, and as we all know that was difficult to manage, which made new libraries such as Redux emerge. This is not backed by any objective figure, of course, only my opinion.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Can you explain this line "State in components is (mostly) a bad idea" are you talking the state handle by Ngrx, Vuex or Redux (Angular, Vue, React... respectively) if that's what you mean, can you tell me where did you get that the industry says that state is a bad idea? I have heard than handling the state of the apps with the tools mentioned above is the way to go. I just want to make sure we are talking about the same.
Hi Pato - what I meant by that is that we used to write state entirely in components, and as we all know that was difficult to manage, which made new libraries such as Redux emerge. This is not backed by any objective figure, of course, only my opinion.