akrumel
From experience, this is critical in a military setting. I find this theory difficult to employ in the technology/startup arena in most cases. That said, the elements which make for an effective and efficient OODA loop are invaluable when building an effective organization. In my experience, many companies miss opportunities because insightful information (observe) often comes into the organization from unexpected sources and does not get properly taken into account (orient); employees have not uniformly internalized the organizations priorities (decision); and decision making cannot be effectively distributed (action).
And thanks for listening about my use case. One concern about using a static function for getDerivedStateFromProps() is that it will not allow for taking instance variables into account. Have not thought through how that might come into play but components certainly allow for this, though many may feel it a strange idea. Perhaps a reference to the component could be passed as well as an additional argument.
I look forward to coming up for air and catching up with the improved approach. Things continue to move quickly and I continue to be impressed at how the changes bring improvement to the ecosystem.
A form of master/detail is driving the need to detect prop changes to fetch additional data while freeing previous data. Consider the master/detail of multiple levels deep driven by route parameters through the ui hierarchy. In RN, this is less of an issue since screens tend to be more focused and ui stack driven. But users working full-time in a complex ui specialized for power users can require much more data/dynamism.