Hey @Jack Tse. No, THAT article is here: https://medium.com/better-programming/react-state-of-the-state-e30e98abdb01
The article we are presently commenting on is intended to drive home the point that when possible, use this dead-simple means for interacting between components.
I should make that more clear.
The ideal is code that explains itself, that is for sure.
Because documentation is another point of change and management.
This is simply the DRY principle.
Experienced developers know that documentation becomes another thing that must be maintained and drifts from the thing it is describing. Just like tests.
Code Complete, dog!
Mythical Man Month yep, that is a real eye opener.
Turns out, I learned a lot from my ’97 Jeep’s manual, too:
Can you be more explicit? I’m not sure what your criticism is exactly.
I spent a lot of time writing Angular and Vue code before even giving React a try.
btw, my dad can definitely kick your dad’s ass :)
I don’t know. Java/JVM may become a more low-level “layer” upon which more dynamic tools are built.
There is something drastically more ‘alive’ and aggressive about the Java ecosystem than there ever was with Cobol.