4 ms·
I’ve built successful large enterprise apps in React, and would recommend it. Here’s how we avoided some of his pitfalls: * Small team of talented developers
by akamaka 6y ago
I’ve built successful large enterprise apps in React, and would recommend it.
Here’s how we avoided some of his pitfalls:
* Small team of talented developers who didn’t always agree on libraries and methodology, but worked through disagreements to reach a consensus
* Recognizing that libraries would change over a two year project, and being ready for major library migration and refactoring
* Writing our own state management tools when needed. Redux is a tiny library. On a two year project, why not create your own custom state management system from scratch, one which makes the .NET people comfortable and has the features that match your project’s needs? It boggles my mind that many devs consider state management libraries to be something sacred, like a compiler, which you would never consider reimplementing yourself on an enterprise project.
- erlich 6y ago> why not create your own custom state management system from scratch Normally "roll-your-own" is bad advice. But in enterprise apps I can see all you needing is an API client with normalized caching (Apollo or `react-query` for REST), and store as much of your page state in your query string, and the rest in React Context. I would reach for Recoil if React Context performance became an issue. But rolling your own comes with so much personal risk if things go wrong - not good for politics.