3 ms·
Everything about this is so wrong. From the "Is this ridiculously clearly named and comically scary name safe to use?" to "Why don't you provide stable API for
by chris_wot 3y ago
Everything about this is so wrong. From the "Is this ridiculously clearly named and comically scary name safe to use?" to "Why don't you provide stable API for some internal state of React itself?"....
- samus 3y agoThe latter is a legit question, for which the answer would be a variation of "it makes future development more difficult for the framework developers" and "please send a proposal for a stable API".
- chris_wot 3y agoTying internals to an external program would be a disaster. That’s why there are APIs…
- samus 3y agoI fully agree. That's why a stable API is needed. But there might be legitimate concerns to not expose such an API as it could impede development. For example, Java intentionally doesn't offer a stable API to extend the compiler. Therefore, Project Lombok has to adapt to each Java release as the OpenJDK project can and will change the compiler's internals at any time.
- SebastianKra 3y agoMaybe, but from what limited information he gives, his use-cases also seem insane. The Stackoverflow post is about detecting the end of a render cycle in useEffect.
- deleted 3y ago[deleted]