4 ms·
That's very fair, do you still think it was a net positive opposed to writing your own component library? https://mui.com/system/styles/basics/ https://mui.com
by uhrush 4y ago
That's very fair, do you still think it was a net positive opposed to writing your own component library?
https://mui.com/system/styles/basics/ https://mui.com/system/styles/basics/
It looks like MUI had some decent intentions in their changes.
https://mui.com/material-ui/guides/server-rendering/#mui-on-the-server https://mui.com/material-ui/guides/server-rendering/#mui-on-...
It also looks like they called out how to address the SSR issue (maybe they recently added these docs?).
I kind of accept this type of friction as a part of libraries changing (As long as the upgrade paths aren't insane).
- jmconfuzeus 4y agoI think we would be much better off using traditional html, bootstrap scss, and some jquery for interactions. But nobody likes to be boring so React it is. React itself isn't really the problem because there are some valid use cases for it. However, it's currently being thrown at every web development problem even when there are better and more stable solutions. But if I had to use React today, I'd stay away from MUI for sure since they constantly demonstrated a lack of maturity.