Material UI VS rsuite

🎨 Project: Material UI 💡 Why Contribute: If design systems and UI frameworks are your thing, Material UI is a must-contribute project. Help maintain or enhance one of the most popular React component libraries used by thousands of developers globally.

Coincidentally, I thought it was this bug that bit you; it was reported a couple of days ago https://github.com/mui/material-ui/issues/43823

To start, I'll be using MUI's Album Template for demo purposes, as I feel that it uses some of the more common components that you'll likely be using. Please note that this repo is template is older so some of the components in it are deprecated.

GitHub: https://github.com/mui/material-ui

Material UI GitHub Repository

The most popular CSS-in-JS libraries are styled-components and Emotion. MUI, a React component library, recently released a promising, zero-runtime CSS-in-JS library called Pigment CSS. This article will explore the features and benefits of Pigment CSS, offering a comparison to styled-components and Emotion based on performance, features, developer experience, and community support.

> [0, 1, 2, -1, 10, 11, 12, 13, 14, -1, 26, 27, 28]

What is that supposed to represent in terms of pagination? Are they cursors...?

> I didn't think the code that generated the HTML from that was really worth testing because it was so superficial.

For what it's worth (as a frontend person), pagination is traditionally one of the trickier things for us to make sure is working correctly. Off-by-one mistakes can happen for example (especially with zero-indexed items). Or sometimes the prev/next buttons don't correctly use the same math as the page 1, 2, 3, etc. buttons. It gets even harder if you don't know the total length in the beginning, or if you allow multiple page sizes or sorts/filters, or use lazy loading, etc.

For those reasons I try to use a ready-built lib like MUI where all that is already tested internally (like https://github.com/mui/material-ui/blob/next/packages/mui-ma... or https://github.com/mui/material-ui/blob/next/packages/mui-ba...), but we still add our own automated and manual tests in our own usages.

But then again I'm bad at math and division, lol, so maybe it's just my own weakness.

The first tool we’ll look at is Pigment CSS, a zero-runtime CSS-in-JS library built to extract the co-located styles into separate CSS files during the build phase and eliminate the need for runtime style processing.

Now open your browser at http://localhost:3000 (in your case address may be different) and you will see an example React application. Let's start hack it. First we will add a navigation bar to our application. We will use React Suite library.

Official Website: https://rsuitejs.com/

React Suite is a set of react component libraries for enterprise system products. It is a well-thought-out and developer-friendly UI framework. (Source: React Suite GitHub)

As of August 2023, React Suite has amassed more than 7K GitHub stars and more than 60K weekly downloads on NPM.

- React Suite looks very nice and clean and the documentation it's pretty straight forward. Has a ton of components built in. The support is ok and the main developer it's pretty responsive on github or on library chat. The main disadvantage is that the library focuses on desktop browsers and not on mobile browsers and uses less for customization.

This example will use React Suite pack of UI components.

website: React Suit

React Suite

React suit is an example of such a narrowly focused component library for enterprise system products.

I'm just starting out developing with Gatsby (or doing frontend in general) and I wanted to add a Navigation bar to my website using React Suite. However, when importing the corresponding stylesheet: