In the world of Front-end developers, "Reactivity" is something that everybody uses, but very few people understand. It's no one's fault, really, a...
For further actions, you may consider blocking this person and/or reporting abuse
Hey Aman, thanks a lot for your post! Couple of thing to know about modern front-end, just for fun:
We should always consider how big our project is before deciding on React/Angula/Vue or just vanilla JS.
Can you elaborate, what you are trying to say?
That reactivity is a real matter for huge projects, and for smaller ones we should double think before consideration.
Thanks for the article, it explains the flow really good.
Ohh yeah totally,
If your are just making a single and simple web page, for some reason, then there is no reason to pick any kind of a framework for that.. Frameworks come into place only when we want things like, scalability, maintainability, etc.
Thanks for the Very clear explanation. Could you also explain how to handle nested components ( watchs).
Thank you :-)
Also, thank you for the suggestion of another good topic, I will surely write a post for that as well.
If any, you can tell me questions regarding this topic (Handling nested components) for which you need an in-depth explanation.
I'm a bit curious about how we handle "target" if there's a nested component. In your example, we put "target" as a global variable. That means only one target can be set at one time. But in the nested component. e.g. component A includes component B
In that case, I want the update of B.data() will only refresh renderFunctionForB(). How can we achieve that?
Very well written. Thank you.
Thanks, Jino. :-)
This is well explained. Thank you!
Thanks, Tirta.
I will try to make even more useful content next time.