4 ms·
My experience has taught me that when developers consistently use your tools “wrong”, it’s a sign that the tools themselves are the problem. The use cases descr
by sickcodebruh 4y ago
My experience has taught me that when developers consistently use your tools “wrong”, it’s a sign that the tools themselves are the problem. The use cases described in this document outline common needs that shouldn’t be so easy to get wrong. It reads like a call to action for an expansion and rethinking React’s public interface via new hooks or utility functions. You can’t always document the pain away. I’m not a React maintainer so I don’t know how easy or possible this is, but considering all the fantastic things the team has done, there’s no way that this is their best.
To paraphrase an old quote, “If you see bad code with your utility all day, perhaps your utility is the bad code.”
- ep103 4y agoJoel on Software - The Pit of Success applies here, yet again
- mcgwiz 4y ago<aside> Joel is a great but credit for this goes to Rico Mariani, originally quoted here https://web.archive.org/web/20100514093413/http://blogs.msdn.com/brada/archive/2003/10/02/50420.aspx https://web.archive.org/web/20100514093413/http://blogs.msdn... </aside>
- gardenhedge 4y agodisagree completely. the problem is newbie devs are learning react without know javascript first
- tadfisher 4y agoI submit that React would have appropriately zero users if it nailed down its API to only allow the "right" way of using it from day 1.
- frodowtf 4y agoReact would have needed its own domain-specific language to get around the implicit reference insanity and other quirks of JS.