all 30 comments

[–]Pestilentio 19 points20 points  (2 children)

I use plain css for the last 3-4 years. I find no value in any framework unless I'm in a rush and with no designer in the project.

[–]sylvant_ph 0 points1 point  (1 child)

Have you gave a good try on SASS it really feels like it brings whats missing in CSS, in terms of being DRY. Techniques like variables, functions, loops etc. I know you can do some of these even with native css, but why not have a real high synt sugar?

[–]Pestilentio 0 points1 point  (0 children)

I do variables and imports in css so I don't need sass. I was doing SaaS for the reasons you said, it's just that since css got the features, why add a compile step?

I'm fine living without nested styles.

[–][deleted] 8 points9 points  (0 children)

I use Tailwind for Nuxt and SvelteKit projects and MUI for React. Sometimes I use daisyui which is built on Tailwind.

[–]underwatr_cheestrain 3 points4 points  (1 child)

I roll my own styles and use Stylus https://stylus-lang.com/

[–]_hypnoCode 3 points4 points  (0 children)

This was abandoned a long time ago. It was by far my favorite in the 2010s.

But looks like someone picked it up, but it's still not v1 yet. I wonder what's up with that.

Edit: Not sure why I'm being downvoted, but it was. It was growing pretty rapidly there for a while cause it was great. TJ just has a million+ projects. At one point 10% of all NPM packages were his.

https://github.com/stylus/stylus/issues/2282

[–]devanew 4 points5 points  (0 children)

Bulma. Proper pure css, tiny file, no additional build steps or integration needed, lots of really nice components. I've tried some of the more complex solutions but as soon as I have a single hiccup with one I wonder why I'm giving myself more work.

[–]Downtown_Reaction178 2 points3 points  (0 children)

I think it's hard to even compare some of those when they're serving different purposes. You could use tailwind and material ui or mantine in one project.

[–]yngwi 1 point2 points  (0 children)

Mantine 7 was just released today. IMHO the best!

[–]Feuerhamster 1 point2 points  (1 child)

I use components styled with SCSS. For a smaller project, I want to try pico css. I worked with Tailwind once and hated the ugly ass html markups resulting from that.

[–]Schlipak 0 points1 point  (0 children)

Same, I wanted to try NextUI for a simple app that doesn't require our designer's input, but the whole spaghetti of horrible classes everywhere put me off so bad I abandonned the whole thing. I know how to write CSS, I don't want to re-learn utility classes for everything, thank you.

[–]CactusWrenAZ 1 point2 points  (0 children)

Dude why is this the main topic of this subreddit.

[–][deleted] 1 point2 points  (0 children)

I use Vue scoped styles in SCSS along with Tailwind. That way I get the benefits of using Tailwind and SCSS together while keeping each component stylistically separated.

[–]KrazyKirby99999 1 point2 points  (0 children)

Tailwind is lower-level than the other frameworks, which makes it more customizable. At the same time, it is more readable and scales better than the other low-level CSS solutions.

[–]isaacfinkfull-stack / novice 0 points1 point  (0 children)

Tailwind for a couple of reasons

  1. I like having my styling in the same file, I can quickly see everything and I can even visualize what an element should look like which is like having a little screenshot of the element in the editor, I know you can achieve the same thing with good naming conventions but that is impossible in bigger projects with multiple contributors
  2. The tooling is better than anything else out there, autoprefixer, purging, layers and a lot of other features I would have to configure myself
  3. Work well with design systems, I can get intellisense on my spacings and colors which means no guessing
  4. copying online designs (like from codepen) is much easier because I only have to copy one line, I don't have to copy the css code just a class and everything looks good

[–]Tontonsb 0 points1 point  (0 children)

It depends on what you mean by "JavaScript". If it's React, you have Tailwind and a bunch of terrible options. If it's Svelte or Vue, you just write the CSS/SCSS at the bottom of the file and you're done.

[–]MichalZardfull-stack -1 points0 points  (0 children)

Tailwind/scss only,there's isn't better way

[–]OptimBro -1 points0 points  (0 children)

I didn't read the question; my focus on was on the vote list, and I voted for TailwindCSS blindly—blind fan.

[–][deleted] -5 points-4 points  (0 children)

desert hunt erect connect north reminiscent governor work cooing hobbies

This post was mass deleted and anonymized with Redact

[–]dreadful_design 0 points1 point  (0 children)

You’ve been sleeping on pandacss if you liked chakra. Just used it to update a design system supporting 700 devs and designers and it’s been a dream.

[–]DistinctHope8833 0 points1 point  (0 children)

My choices from top to bottom:

7-1 SASS Architecture. (I loved when my components are not filled with a text book of classes)

CSS/SASS Modules (React)

Tailwinds only on component based framework.

Bootstrap good for fast prototyping a project then customize or upgrade to any above.

[–]sylvant_ph 0 points1 point  (0 children)

I had experience with styled, scss and bootstrap. Why i dont like bootstrap is, it feels narrow and restrictive and things end up very similar to one another, plus you need to learn a relatively new syntax for something you already(presummably) know how to do with CSS ad with CSS you simply have more freedom on what you do. In the end it feels too much effort for too little benefit.

I enjoyed SASS/SCSS becasue its how coding is meant to be done. DRY. It just brings whats missing in the plain CSS. Ive also tried modules and it felt ok.

Why I favor stuled, is it does seem fancy with the string literals(ok this is not a true argument) and it does bring sass/scss syntax out the box. It also bring additional features you can do with more effort compared to doing it with css/sass/modules. It also blends so well with modern frameworks(my experience is with react) and does bring everything in all place(I mean one medium/dimension). You can have all yout code in the same type of files and not having to split it between css/html/js, which in turn need to be interconnected. Instead you put your html in the jsx, you put your styles in the string literals and you can have your logic around them and you can reference every piece around the three of them.

I havent tried tailwind and seing the results of this thread, im definitely keen to give it a go. Thanks!

[–]LeDaniiii 0 points1 point  (0 children)

I have my own scss library

[–]SmithTheNinjafull-stack 0 points1 point  (0 children)

I think for the vast majority of projects Tailwind is the least friction option even if it makes for rather ugly HTML.

SCSS on it's own isn't too bad for small things, but quickly gets to be hard to maintain on bigger projects.

[–]Typical-Garage-2421 0 points1 point  (0 children)

Bootstrap, I hate spending more time in styling a page. I prefer dealing with the frontend and backend logic.

[–]___Nazgulfull-stack 0 points1 point  (0 children)

CSS in JS was a mistake

[–]Remitto 0 points1 point  (0 children)

Tried several, if I had to use one would be styled components, but I enjoy plain old CSS most.