3 ms·
I did the following, still comfy with react. - Got rid of redux because it's shit - Got rid of Material UI because it's bulky and its API changes are painful,
by joshxyz 6y ago
I did the following, still comfy with react.
- Got rid of redux because it's shit
- Got rid of Material UI because it's bulky and its API changes are painful, replaced it with tailwind
- Got rid of React Router because it's bulky and its API changes are also painful, replaced it with a simple hook
- finiteseries 6y agoI haven’t used react since 2017, but the fact that react-router is still undergoing painful API changes somehow doesn’t surprise me.
- idkwhoiam 6y agoHow did you replace Material UI with Tailwind? You mean you reimplemented all the components it ships with?
- joshxyz 6y agoWell that's just impossible. What I just noticed was that when I looked deeper on MUI components, their internals are bulky and almost always used a mixed of JS & CSS instead of just CSS. They even import an external library for their styling. On low-end devices it's a bit too much (I'm talking about edge-case users with phones as cheap as $50). It was also quite a chore keeping up with their API changes every couple months. I forced myself to cut down on components and just style my UI with CSS. It's more consistent, more predictable, and less strain on the end-user's device. It's a trade-off across looking good, better end-user performance, good user experience, good developer experience, and having more time for the product and users instead of maintaining and updating dependencies.