3 ms·
Go with React and a charting library like Nivo. Write wrappers around Nivo so you can switch out Nivo with something else that might handle particular charts be
by runawaybottle 6y ago
Go with React and a charting library like Nivo. Write wrappers around Nivo so you can switch out Nivo with something else that might handle particular charts better. Don’t marry a charting library. Pick a small Redux alternative for global state management (haven’t tried Recoil, but maybe Recoil?). That will hopefully keep your frontend light and away from an industrial (too big to ever refactor, too intertwined to ever pull things out or change paradigms) codebase.
Your backend can be anything that serves up a rest api. Otherwise go graphql.
- Raed667 6y agoRedux is still a very valid choice. If you don't like the setup boilerplate, you can use the official toolkit which has very sane defaults. https://redux-toolkit.js.org/ https://redux-toolkit.js.org/
- runawaybottle 6y agoWhat can I say, you can’t teach people taste.