If you are looking for a component library for your next project, there are tons of options for you like Material UI, Chakra UI.etc. I have used CSS frameworks like Bootstrap, shoelace.js.etc. But, do you really need a CSS framework in 2022?
What do you think? 👇👇
Oldest comments (18)
It depends on the person really. I personally use a css pre-processor (sass) to write my code and since I've recently started to create projects using nextjs, I don't really want to overload the js files if I use something like tailwind so using sass modules is ideal afaik in that specific scenario.
sass is a brilliant tool to use 🚀.
In my preference we actually don't need any css frameworks in today's date. The reason being that we have a lot of websites in today's date which provides prebuild elements with html and css which a developer can use to hack through some repetitive process. And in terms of performance always
CSSwould always beat all others 👨💻.And let you assure you that a engineer needs a good sense of design knowledge and working with
CSSwould improve it in time . So future developers would be able to make amazing looking websites in a quick and clean way ✌.Couldn't agree more 🙌
If you stay true to your css structure it's far more easier designing everything by yourself. Most experience in structuring I gained by looking through code of other frameworks and adapt suitable improvments for me.
Right Supportic. It takes time for developers to understand this but as someone dig deeper into web development they understand this fact 👍.
The larger and more diverse your team is, the better a fit are component frameworks, because they partially normalize the lack of design/styling skills.
CSS frameworks are a matter of scaling. Huge project with plenty of people involved absolutely need it. A portfolio maintained by a single person definitely don't need it.
Still, there are a lot of reasons to use it even when you don't need it. Most people are decent, but not good, at CSS. Writing custom CSS therefore quickly escalates to a mess. Sticking to a UI library can very often save you from that.
Anyhow, if you only plan to use a single or a few components from a library, you're probably better off without it, IF you know how to write the compontent so it works well.
I do it all the time. Most of the time, when I install a component library, I do so for a single component or two 😄. Even though I am decent enough with css grid flexbox and layout system, I don't believe in my design skills yet. Most of the time, I do the layout myself, and use a prebuilt component library.
CSS frameworks nay, component libraries yay! Most component libraries today include some way of doing CSS-in-js. For example Mui components ship with an
sxprop that you can use.I usually write my own css for most of my personal/individual projects. Because using frameworks and component libraries make me feel strict. Additionally, they provides tons of code which I don't use.
But for those projects which need to be handled by multiple developers, I prefer using frameworks or libraries.
Component based libraries are for the 80% use cases. Like a normal open source website page or projects which are trivial enough that it doesn't need a highly customised website.
The rest still needs CSS or Tailwind CSS which is utility class based.
It's a mix of both. Never one sided.
If using any of these component libraries means reducing the development time immensely than go for it. Time is money, and clients don't care how you get the job done.
Yes. tamagui.dev is the best of all worlds: fully cross platform, compiles out CSS with media queries on web, gives a RadixUI style of ARIA compliant base components to build on, provides some components you can use wholesale, or customize at will, using a Tailwind inspired API.
I will definitely check this one out ✨
mui is very convinent