mantine VS Material UI

🔗 https://github.com/mantinedev/mantine

Mantine is a comprehensive component library with built-in React hooks to make development easy. With large community support, every aspect of Mantine is free and open source. Mantine stands out based on the following features:

Honestly I wouldn’t personally, I’d use a really good components library like https://mantine.dev/ (no affiliation, just a fan) and make your site look similar to your competitors. That’s what people seeing your pitch will expect IMO. Depending who you’re pitching to they might not use a terminal very often.

The Mantine NextJS App Router + Nextra Template is an outstanding resource for developers looking to harness the power of the Mantine UI library, the NextJS framework, and the Nextra documentation template. This combination delivers a robust platform for building responsive, modern, and accessible websites efficiently.

Link: https://mantine.dev/

Website: mantine.dev

The https://mantine.dev docs rule. They provide a lot of examples on the landing page and if you navigate through the page each component has a great explainer with a playground and all possible settings you can give. Direct with links to the source code and a great CMD+K search.

A friend of mine who is good at these things recommended https://mantine.dev/

MUI is the OG of UI component libraries. They’ve been at the top back since when Bootstrap was a contender and are still maintaining a top spot in the era of Tailwind and other UI libraries. With more than 95k GitHub stars (and counting), and top companies using it in production, I’d say this is the open-source React component library with the most stars. MUI also has paid components available for enterprise users.

🎨 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.