Part of React's philosophy is to provide escape hatches, for when the idiomatic patterns break down. This is great! But... when it comes to the core parts of your architecture (shared components and frameworks), you should try to avoid cheating as much as possible. 
It's not just that these anti-patterns may lead to bugs. It's that they suggest deeper architectural flaws that could create bigger problems in the future.
The React team's job is to identify why people resort to cheating, and provide them with a more idiomatic solution.
The React team's job is to identify why people resort to cheating, and provide them with a more idiomatic solution.
Hence: React Suspense, getDerivedStateFromProps, the new context API
All our best features arise from things that used to require cheating. Next time you're tempted to cheat, reach out to us! We may already have a better solution for you. If we don't... let's build it!
All our best features arise from things that used to require cheating. Next time you're tempted to cheat, reach out to us! We may already have a better solution for you. If we don't... let's build it!
