USER
As an expert summarizer, your task is to condense the following text into a clear and engaging summary in the same language as the source. Begin with a "TL;DR" that captures the core message in a single sentence, followed by a more detailed summary. Use appropriate emojis to highlight key points or emotions, making the summary visually engaging and easy to skim. Ensure the summary accurately reflects the original content's intent and tone. Here is the text to summarize:
I like SCSS more than Tailwind. Should I be ashamed? (self.Frontend)
16 saat önce Powershow_Games gönderdi
Just be honest
161 yorumpaylaşkaydetgizlegammazlacrosspost
toplam 161 yorum
sıralama ölçütü: en iyi
biçimleme yardımıiçerik politikası
save
[–]sabba_ooz_era 123 puan 16 saat önce
It’s a shame that this is even a thing. Use what feels most comfortable to you.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]okaywhattho 8 puan 15 saat önce*
Never understood it. Who cares what you use if you get the job done.
I can only understand the argument of showing up somewhere new and having to learn something new in the process. Still doesn’t feel like it’d hurt to pick up something new.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]devolute 1 puan 59 dakika önce
Who cares what you use if you get the job done.
Who cares? Colleagues. People need to be using the same tooling to not have a shit time. That's who cares.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]lynxerious 1 puan 9 saat önce
its not a thing I feel like OP is hallucinating
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]OhBeSea 100 puan 16 saat önce
Why would you be ashamed?
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]TheOnceAndFutureDougLead Frontend Code Monkey[🍰] 58 puan 15 saat önce
Because teh hype train is very loud and it can make people feel insecure.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]hoppyandbitter 3 puan 4 saat önce
It’s funny though, because I never see Tailwind users shaming or pressuring people for not using it, but I always see non-Tailwind users shitting on it and complaining about people who use it
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Powershow_Games[S] 7 puan 12 saat önce
This
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Strict_Link_3409 1 puan 13 saat önce
Haven't seen the hype at least not in the companies I've worked with, we usually have a standard and stick with it. Neither is wrong, just whatever makes it easy for making the UI.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]TheOnceAndFutureDougLead Frontend Code Monkey[🍰] 3 puan 12 saat önce
Hype trains aren't usually in companies. On Reddit and other social media platforms, however...
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Shaddix-be 0 puan bir saat önce
Yeah, even the marketing around Tailwind feels like "you would be stupid to do it any other way".
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]codernaut85 123 puan 16 saat önce
No, I feel the same way. Not a fan of Tailwind at all.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]JayV30 37 puan 15 saat önce*
Yeah, I hate Tailwind. I once worked at a place that used Tailwind and I didn't really have a say in the matter. But I also didn't have time to learn it due to the pace of work. So I just wrote SASS and ran it through an online converter to generate the Tailwind classes. A stupid, insane extra step.
EDIT: JFC, people. Yes, I "learned" tailwind. But I didn't have time to be slowed by not being efficient with it. Also, anyone who knows CSS has "learned" tailwind. The rest is just memorizing their classes through repetition. Think what you want, I think Tailwind is mostly popular with people who never bothered to learn CSS.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]torocat1028 17 puan 15 saat önce
do you really hate tailwind if you didn’t learn it? not a big fan of it either but it’s not that bad to learn i think
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]TheOnceAndFutureDougLead Frontend Code Monkey[🍰] 10 puan 15 saat önce
Hate is a strong word. I've tried it a few times and I just don't see the benefit, personally.
But I don't hate it any more than I don't hate CSS-in-JS. It's just a tool I don't like and don't want to use.
Ember I hated. Mostly because it wrapped everything in a div whether I wanted one or not and it made writing clean markup harder.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]JayV30 0 puan 15 saat önce
Well, I learned it I suppose. I did a course. But I never got fast with it, so I just stuck with CSS.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]j0nquest 5 puan 15 saat önce
So I just wrote SASS and ran it through an online converter to generate the Tailwind classes. A stupid, insane extra step.
I don't like TW that much either, but come on? Was that really worth not just RTFM?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]JayV30 8 puan 15 saat önce
Yes, because TW is css with classes, so I just wrote the css instead. Could I have done it with TW? Sure, but it would be slow because I wasn't practiced in it. And I had too much work to do.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]GingerVking -2 puan 15 saat önce
This is the dumbest shit I’ve read in a while
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]GoatBass 0 puan 3 saat önce
Tailwind haters can get quite emotional for some reason.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]its_Azurox -2 puan 13 saat önce
I don't understand how you can say that tailwind is popular for people that don't learn CSS, it's literally pure css ? Maybe the only real abstraction are the group/sibling thing, the rest feels like writing css
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]ntmfdpmangetesmorts 1 puan 9 saat önce
How can you use tailwind if you dont know CSS ? Lol And no, its not because you know css that you know tailwind. You will understand what the tailwind classes do sure....but if you dont know the tailwind classes you dont know tailwind.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]ntmfdpmangetesmorts -3 puan 15 saat önce
So yeah you cant even be bothered to learn it lol kinda makes your point moot
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]spider_84 36 puan 16 saat önce
Yep, tailwind is rubbish.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]MarketingCoding 8 puan 15 saat önce
Tailwind was ok for quick prototyping (once you remember the format) but like most of these libraries as soon as you get a complex design it gets unmanageable.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]lWinkk 2 puan 13 saat önce
How?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]the_reven 5 puan 8 saat önce
when your bosses decide yet again to completely redesign your app and you have to go and change all those hard coded classes everywhere instead of minor modifications to some (s)css.
Been working on the same app for 18 years now, its been through many technology changes and way more style changes.
Now with css variables and scss , a design change is usually fully achievable by a day or two of scss changes by a single dev that doesnt impact other devs and isnt a merge nightmare.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]ohlawdhecodin 1 puan 4 saat önce
Now with css variables and scss , a design change is usually fully achievable by a day or two of scss changes by a single dev that doesnt impact other devs and isnt a merge nightmare.
Only if the codebase was properly written with understandable and "meaningful" css. In any other case it may be an absolute mess of neted and broken hierarcies and tons of inheritance/cascade problems.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]the_reven 2 puan 4 saat önce
Yeah but in that scenario tailwind doesn't work either since of the same mess.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]ohlawdhecodin -2 puan 4 saat önce
Exactly. So, I think, it's a matter of preference and convenience.
Vanilla CSS: perfect for freelancers and solo-devs.
Tailwind: perfect/mandatory for a team environment, to prevent people from going completely wild and coding their own custom css
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]DaRizat 2 puan 11 saat önce
I've found in most settings where I've worked with Tailwind with teams, it's because there are probably 5 classes on each div that don't actually contribute to the visual effect trying to be achieved.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]mittyhands 4 puan 11 saat önce
Unlike CSS or SCSS or CSS-in-JS styles which never have irrelevant styles
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]esr360Front End Developer 2 puan 8 saat önce
I mean if you know what you’re doing, no, they don’t, and shouldn’t.
You can, and should, be able to explain what each and every CSS property that is applied to an element is doing, and if there is a property not doing anything then it shouldn’t be there.
I will grant you that this is very difficult to achieve, but it is more than possible. I’ve worked with one team a couple of years ago where we were achieving this.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]mittyhands 1 puan 54 dakika önce
My point was that this is possible to do in any styling paradigm. It's not a tailwind-specific thing to have unused styles.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]esr360Front End Developer 1 puan 53 dakika önce
In which case yes I totally agree!
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]DaRizat 3 puan 11 saat önce
And indeed, this is one of the reasons I am a proponent of TW, because it is much easier to debug and refactor rather than going back and forth between styles and also not knowing if refactoring a class would have side effects on another element which uses that class.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]lWinkk -3 puan 11 saat önce
5 extra classes is complexity?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]olivicmic 6 puan 10 saat önce
When classes that are semantic and identifiable are replaced with classes that represents style properties it can make debugging difficult. This is something I experience with the team I am on and their existing project: there can be buggy component, but the class is a combination of non-unique style classes, so I cannot search the project for a unique class, find the file and fix the component. I have to have existing knowledge of the code in order to fix anything.
Now this isn’t an argument against multiple classes, you can have an identifier class alongside those 5 style classes, but why not K.I.S.S. and have the styles within that identifier, and use mixins for repeated style patterns.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]DaRizat 3 puan 11 saat önce
I'm just saying class bloat is the #1 reason TW can become unwieldy. In my experience it is rarely necessary and a lot of times you can achieve the effect with less classes or proper nesting. Im definitely a tailwind advocate, just calling out when I have seen it in need of repair.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]lWinkk 3 puan 11 saat önce
Yeah but that’s not complexity. That’s just people that don’t know CSS enough to be good at it. If they wrote shit tailwind, they’ll write shit CSS.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]DaRizat 1 puan 11 saat önce
Agree, and that's why I like tw because it's much easier to spot shit and not worry about correcting shit having other side effects if classes are renamed
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]SHOW_ME_UR_KITTIES 13 puan 15 saat önce
With all technologies/libraries, there’s a time and place for it. The problem is somehow when developers see that everyone else is using a new framework, library it must be really good and work for all use cases. That’s not the case.
Tailwind does one thing very well in that it establishes utility classes and abstracts away the need to mess with individual styles.
This is a HUGE benefit when you’re working with large teams, where developers have very different backgrounds and differing levels of understanding of css, and large projects where you need to maintain consistency.
It sits right between writing SCSS from scratch and maintaining your own styles, and BootstrapCSS.
It also adds the benefit of tree shaking in that it only includes what’s used in your code and leaves everything else out of the bundle.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]lowfour 5 puan 10 saat önce
This guy gets it. There are so many shitty coders writing horrible css (let’s not even talk scss) that front ends are incredibly inconsistent. Random margins and paddings, such a mess. Tailwind is fantastic to keep a certain mental coherence to all that even if you have a lot of junior FE. I have been using extensively scss with our own mixing for over 11 years and I am not stopping using tailwind. Speed and consistency. And sometimes I still need to use scss for something really specific. Often tailwind offers incredibly low payloads once compiled. In any case, just use whatever pleases you and gives good results.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]composero 16 puan 14 saat önce
Dude, SCSS gives you far more control. It’s better than throwing 50 classes to get a button to look right (I’m exaggerating of course)
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]ohlawdhecodin 1 puan 4 saat önce*
better than throwing 50 classes to get a button to look right
Even if you use Tailwind, aren't you supposed to create a ".mybutton" class that incorporates all the main styles (color, border, shadow, font, padding, line-height, etc) and then, only when you need them, you apply some utility/Tailwind classes, based on the layout needs?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]machopsychologist 1 puan 2 saat önce
Exactly.
If you reach a point where tailwind no longer works in a specific case, go back to vanilla or use tailwind @apply.
The point is you choose when you break out a class and minimize the creation of classes. Not start with classes by default.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]composero 1 puan 2 saat önce
You definitely can, but I’ve seen more code that doesn’t do that than does do that
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Powershow_Games[S] -1 puan 14 saat önce
Yeah I can't use Tailwind without asking ChatGPT what to do every 2 seconds
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]howaboutsomegwent 1 puan 13 saat önce
it does feel quite inefficient to have to learn both the tailwind class names AND the vanilla css properties and values that underlie them, at that rate it’s just quicker to write css since you’ll need to understand css to use tailwind correctly anyway
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]lynxerious 0 puan 9 saat önce*
if you cant use tailwind it means you dont know css tbf, its literally pure css, and translating the css to tailwind class is simple
if you dont like it thats fine, but complaining that you have to "learn" something to use it is absurb, much less something as simple and straightforward as tailwind
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]physiQQ 1 puan 3 saat önce*
There definitely is a learning curve to Tailwind coming from CSS. Not all properties are similar and there's a limited set of values for each one.
color = text line-height = leading letter-spacing = tracking
As someone who just started to learn Tailwind, I don't know the Tailwind way of doing things at all, so it's very common for me to Google stuff like "line-height tailwind". Even when I do know line-height is "leading", then I still don't know the accepted values of it.
Sure, my IDE can list me the possible values, but I think it's not all that convenient.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Citrous_Oyster 25 puan 16 saat önce
No, feel liberated.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Whalefisherman 7 puan 15 saat önce
No my friend. Whatever gets the job done. We won't shame you for using SCSS and you shouldn't shame yourself either. Just use what works for you! (I'm a big time tailwind fan saying this to you)
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]anonssr 20 puan 15 saat önce
Frontend is a weird area where people seem to be having the need to have radical opinions of whatevers going on, do something in the opposite direction, become mainstream, then hate it again because it's mainstream, come up with something radically different, and repeat.
It's barely ever about the users, and most of the time it's about the devs, for no aparent reason.
Css in particular had a bunch of these. We had inline styles, then moved to stylesheets, the IDs bad, then it was all classes, then having different stylesheets to organize was good, along the way things like bootstrap apparead, then having stylesheets was bad, then pseudo languages, then we didn't want either, then we had css in js, then bootstrap was bad but we still wanted helper classes, them tailwind took helper classes to an extreme, now we are back to hating small helper classes.
In my opinion, tailwind is a fancy way to write inline styles, it doesn't help a lot in really big projects. But it's whatever, it's gonna be legacy in a while and we'll have something new to circlejerk about.
I swear, frontend goes through this things at a much higher pace than any other technology and I don't know why lol.
I'm ranting but back on topic, no, pick whatever helps you build and maintain your projects. You'll eventually figure out when and why yo use each thing. Claiming one is best over whatever approach is not the way to go, tools are designed for specific jobs, there's no tool for all of them.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]m0rpheus23 5 puan 15 saat önce
Hehehe. I do this rant every few weeks. Frontend is just weird
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]supaami 5 puan 15 saat önce
Nah, just use whatever to get job done. People should stop identifying themselves with the tools they use.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Bridge4_Kal 12 puan 16 saat önce
No you shouldn't be ashamed. SCSS is amazing and even better than tailwind if you know how to utilize all its features like mixins and loops and tons more. Just know the job market favors tailwind these days.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]bananas_are_ew 2 puan 9 saat önce
someone finally said it. knowledgeable use of mixins, maps, functions blow tailwind out of the water. the 5 classes one has to continuously repeat across however many components can just become a mixin. something needs to change? update the mixin. the mixin needs to fork? add an argument. but frontend devs aren't very good at css anymore so they'd rather do the most instead of learning what is now native css features.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Ratatoski 2 puan 9 saat önce
I like mixins for this very reason. But Tailwind had our total weight of CSS be 4kb for the whole org website. I've not really gotten over that we went back to SCSS and I'm looking for smarter ways to use it
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]repeating_bears 1 puan bir saat önce
had our total weight of CSS be 4kb for the whole org website
But some of that is just shifted to larger class attributes in the HTML. A fairer comparison would be total amount of HTML+CSS.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Ratatoski 1 puan bir saat önce
Some if it yes. But neither sides matter when someone slaps an uncompress 20MB image on the page :)
But one thing I like about Tailwind is that once I delete or change the component the CSS is automatically deleted/updated. There's no hunting around to verify that all the SCSS you're loading is actually still in use. (But if there's scripts for that with SCSS and React I'm totally down)
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]tiny_smile_bot 1 puan bir saat önce
:)
:)
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]tluanga34 24 puan 16 saat önce
Tailwind is just a bootstrap regen . Scss is a different animal
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]metal_slime--A -4 puan 15 saat önce
Thank you! How is tailwind not essentially bootstrap reborn?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]lamb_pudding 8 puan 15 saat önce
They’re completely different. Bootstrap is giving you things like components, utilities, and a grid system. You have class names like .card for example that will give you a card component which comes with a number of CSS styles on it.
Tailwind doesn’t do any of that. Tailwind is giving you class names that each map to one CSS declaration. There’s no .card component. If you want a card that’s a component you make in your template system and you add the CSS (Tailwind) you need to style it.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Neither-Upstairs -4 puan 15 saat önce
Just use CSS lol
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]lamb_pudding 7 puan 14 saat önce
Been writing CSS professionally for 15 years. I love it. 8 times out of 10 these days I am going to go with Tailwind (with JIT mode).
My reasons for preferring it all boil down to the HTML and CSS being closer to each other which means:
My HTML and CSS are in one file, I don’t have to switch between them
I don’t need to come up with a class name to target everything I want to style
When I delete the HTML I know I don’t have to track down styles that may no longer be used
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Neither-Upstairs 7 puan 14 saat önce
I’ll never understand the argument of “I don’t have to name things”. Honestly it just makes things harder to track down and naming things is not that difficult.
Having a separation of concerns between HTML and CSS is not a problem that needs to be solved.
The mess of an HTML document is horrifying.
To each their own, it’s just not for me.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]da-kicks-87 1 puan 14 saat önce
If you work with a team and your co-workers suck at naming... That's why. I have seen some bad things.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]mrkingkoala 0 puan 13 saat önce
I prefer html/scss myself. But Tailwind in a team makes sense due to naming conventions and keeping everything standard.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]xXxdethl0rdxXx 4 puan 13 saat önce
I truly don’t understand the naming part. Isn’t there semantic meaning and value in a class name? Would you prefer not having to name functions and variables in JavaScript as well?
The other two points I feel like could be solved with tooling.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]howaboutsomegwent 1 puan 13 saat önce
yeah that’s my main issue with Tailwind too, I tend to prefer working with semantic classes too because they have a documentation value/they make html more readable as an added benefit. Plus, you can still write utility mixins similar to Tailwind classes, and then combine them into semantic classes. Best of both worlds. Maybe I’m missing something but I haven’t yet found any scenario where Tailwind is better than properly used SCSS.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]DaRizat 1 puan 11 saat önce
What's more declarative than the actual css properties you're trying to put on an element? If you take the week or so it takes to translate what you already know of css to tw class names, you can basically just read a piece of markup and understand what visual effects are applied.
It's also much easier for me as a lead dev to look at a component with tw classes on the elements and pick out bloat that isn't contributing to the visual effect than it is in a class in a separate file, especially with nested divs.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]Bridge4_Kal 2 puan 14 saat önce
My HTML and CSS are in one file, I don’t have to switch between them
One of my favorite draws of Svelte (and some other frameworks too). But you can write your style tag with scss or postcss right there in the component file under your html markup. But you're right, Tailwind makes complete sense and is quite useful, especially with React.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]iblastoff 2 puan 12 saat önce
all of these 'benefits' are absolutely hilarious.
never heard of a single dev complaining that they have to 'switch files' in order to write code lol. thats like saying you shouldn't be separating out components/functions/whatever and should just put them all in one file so you dont have to 'switch files' so much. NOT a real benefit.
naming classes? oh no! i mean you're already naming functions arent you? are you saying a dev of 15 years you're still having trouble naming shit? my god.
aren't you already abstracting components anyway?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]lamb_pudding 2 puan 12 saat önce
Why are you so sour? These are the benefits I've gotten from Tailwind and why I reach for it. I'm not complaining about any of these. Yeah, switching between files is something I do all day. But you know what I've found, it's way quicker to take a design and implement it in HTML and CSS when using Tailwind. A good chunk of that speed up is being in one file and not having to name my class names.
I thought it was a dumb concept until I actually used it on a real world project. I was sold. Most teams I've worked on have come to the same consensus. If you don't want to use it, don't use it. If you actually want to have a discussion on it and have used it on a large project in production happy to converse.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]reboog711 -1 puan 13 saat önce
My HTML and CSS are in one file, I don’t have to switch between them
The programmer in me cringed, and screamed you're not separating your concerns.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]itsjustausername -1 puan 14 saat önce
Daisy UI: The most popular component library for Tailwind CSS
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]saintpumpkin 3 puan 15 saat önce
you are comparing apples with oranges
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Powershow_Games[S] 1 puan 15 saat önce
How so?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]TheTomatoes2UI/UX + Frontend 2 puan 14 saat önce
nothing prevents you from using TW and still write your own CSS/SCSS files
TW is literally just premade classes that contain single CSS props (99% of the time)
SCSS is a superset of CSS that makes it a lot easier to write
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]da-kicks-87 3 puan 14 saat önce
It's not good practice to add your own CSS classes when using TW. There are some exceptions when I do, but it should be avoided.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]TheTomatoes2UI/UX + Frontend 1 puan bir saat önce
But then how do you create reusable groups of multiple properties? Just defining a const string in a cssClasses.ts file?
Or a long list in the TW config file?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]ledmetallica 3 puan bir saat önce
I absolutely hate Tailwind. Littering your HTML template (in Angular, in my case) with Tailwinf class names makes my OCD trigger up. It clusters up the template heavily, code formatter tend not to format a long class attribute string, so Tailwind class names tend to just stretch out past qhatever page width you set in your formatter, and most people (my current team especially) have no idea how to properly use Tailwind in the first place.
There is a benefit in Tailwind, where you can create a library of components that is meant to be shared across multiple apps. The Tailwind class names that you tattoo onto the components template allows you to have uniformity of style, regardless of the environment you're injecting the component into.
But when you're just working on a single project, using SCSS or even vanilla CSS is so much better, imo
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]m0rpheus23 2 puan 15 saat önce
I am a proud user of SCSS and Bootstrap if the need arises. Use whatever works for you
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]billybobjobo 2 puan 15 saat önce
Only for making this kinda post, not having the preference. :P
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]TwinnyNO 2 puan 15 saat önce
As long as the food tastes great and your guests are happy, no one cares whether you used a slow cooker or a frying pan to make it.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Ok-Armadillo-5634 2 puan 12 saat önce
I don't like tailwind i have been doing css for 15+ years though and don't really need any kind of library for it at this point. At least it's not that BEM or css in js bullshit though.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]s3rila 3 puan 16 saat önce
You should be proud
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]n3onfx 4 puan 16 saat önce
Why?
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]chrissilich 4 puan 14 saat önce*
No. I’m with you. SCSS makes much more sense to me, I think because I come from a design background, so I think about the broad design system, and making the big systematic choices first, and then narrowing down. I guess you can do that with tailwind, but it doesn’t feel organized properly. SCSS feels like a brand guide in an organized book form. Tailwind feels like a brand guide written out on 200 individual post it notes.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]throwtheamiibosaway 2 puan 9 saat önce
No, people should be ashamed of using tailwind.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]herbertdeathrump 2 puan 16 saat önce
You can like both. Most larger corporations have decided to go with Tailwind after thorough analysis. At my large company SCSS has caused us a lot of tech debt, performance issues, build issues, inconsistency, poor developer experiences and other problems on our 100's of codebases. Tailwind has resolved these issues for us across the entire company.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]redditfuckingsuckslo 6 puan 15 saat önce
how can SCSS meaningfully contribute to performance issues?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]herbertdeathrump 1 puan 15 saat önce
We have around 12 years of CSS bloat. We have a metric that we need to meet for TTFP and we are failing it. Our Tailwind compilation passes and in some cases is 14kb or less.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]lWinkk 1 puan 13 saat önce
Yeah tailwind haters gotta just go in the legacy sass codebase for a while. My company had 12k instances of “!important” in the codebase. On top of inline styles and inline stylesheets. You can’t even bloat your shit with Tailwind. It’s not even possible.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]TheGreaT1803 0 puan 15 saat önce
We are facing this right now. Though how do you migrate an entire codebase of scss mess to tailwind?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]herbertdeathrump 2 puan 15 saat önce
For us we have moved from a mono repo to micro frontends. We have a really solid and well thought out frontend template. This template is made up from Next, Storybook and Tailwind with Devbox that runs all the necessary services automatically. Every new project starts with this template and we rebuild things as layers. Every project is mostly the same and consistent which is great for developers that get moved to different projects. Our CSS bloat has decreased significantly and we have consistent styling that works well with the design system and we can import our design system components with no issues.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]TheGreaT1803 2 puan 15 saat önce
So I guess my concern is that either you are full tailwind or full css. But if you try to migrate gradually, youll have to live with excess stuff for the time which might affect performance. Is this right?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]itsjustausername 1 puan 14 saat önce
How are you transitioning between MFE's when they are written in Next? Do you have a shell project which bootstraps them?
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]vsjetrug 2 puan 15 saat önce
Convert the scss to css and add it to the css file that contains the tailwind directives. Reference: https://tailwindcss.com/docs/functions-and-directives
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]InternetArtisan 1 puan 15 saat önce
I don't think you should be ashamed.
I still live by the idea that the only rule is that it has to work, and you're not building something that's a hot mess that someone else has to deal with down the road.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]No-Moment2225 1 puan 15 saat önce
No shame. Remember the client doesn't know which library, technique, etc you use. If you work for a company, and they hired you to use Tailwind, well...just use it for your job and if you have a side hustle, hobby-projects or other freelancing clients then build your projects with SCSS. And just remember influencers make money from hype, they're not necessarily interested on what's the best tool for you, just what makes them money from views.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]TheTomatoes2UI/UX + Frontend 1 puan 15 saat önce
Huh?
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Small-Gas5454 1 puan 15 saat önce
I like both hehe, sometimes in the same project
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]louisstephens 1 puan 15 saat önce
Don’t be ashamed at all. I took the “traditional” route a long time ago: tables -> css -> sass/scss -> css-in-js/tailwind. I have built a few css frameworks for internal use and I really do prefer writing vanilla css. That being said, tailwind has allowed me to crank out one off landing pages for work without much extra effort which I do enjoy. Use whatever you are comfortable with and you definitely don’t have to ride the hype train.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]bozdoz 1 puan 14 saat önce
No
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Doomwaffle 1 puan 14 saat önce
SCSS is beautiful, but with nesting CSS you... you might not need your build process anymore. Sorry, that's still pretty painful for me to say as someone who has lovingly hand maintained my gulp configuration for years and years, even through the 4 to 5 switch, SASS not making any sense as it's own module, and all sorts of things... all lost, like teardrops in the rain...
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]vash513 3 puan 14 saat önce
We still use it due to mixins and functions
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]da-kicks-87 1 puan 14 saat önce
What's so good about SCSS mixins and functions? Use JS for programming. Native CSS has variables and nesting.
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]application_layer 1 puan 14 saat önce
You should not be ashamed. At the end of the day, if the tools you use allow you to be more productive and to give the clients the products, solutions, or results they hired you for, use whatever tools you want.
However, the above is in a freelance or agency context.
If you are hired as a developer by a company that uses Tailwind, I am afraid you do not have a choice but to jump on the hype train. You might be able to convince your bosses to let you use SCSS eventually, but that will only happen after many years, after they have trusted you, if you are a valuable team member they can't lose, or if you are a senior/rockstar developer who can influence company culture and workflows.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Marble_Wraith 1 puan 14 saat önce
I'd suggest upgrading to postCSS.
It's more of a pain to configure, but at the same time you can get way more out of it.
SCSS is easier setup, but TBH most of the features are covered in vanillaCSS now. Probably the only useful one that isn't is loops, and in those cases you can often bake whatever change you need into a scoped component.
As for Tailwind...
It does have some use cases. If you're using React, or some other framework that doesn't treat CSS as a first class citizen. Often times Tailwind (or some other lib like vanilla extract, pandaCSS, etc), is the easiest way to get styling co-located with your component without baking the styles into the component (and messing up the rendering process as a result of having CSS-in-JS).
But other then that. Tailwind isn't really anything special.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]TheStoicNihilist 1 puan 14 saat önce
Ten Hail Mary’s
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]noizz 1 puan 14 saat önce
As a SCSS enjoyer, I read Refactoring UI book (and played a bit with Tailwind). A lot of the patterns they use took me years to discover, some were new to me or just smart. For a team, a consistent resource like Tailwind is great, I've since moved a few different internal design systems towards some of the ways they handle their scales in naming, among other things.
As a whole though, I find Tailwind an overkill, but that's the price you have to pay for catering to so many different use cases.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]reboog711 1 puan 13 saat önce
Me too, but I don't think they are filling the same need in our toolsets.
I don't know Tailwind that well, but I was under the impression it was a set of predefined classes. Bootstrap offers something similar. I've worked with Bootstrap in the past with success. I bet I could work with Tailwind and have similar success.
However, SCSS is a pre-processor, with variables, nesting, and mixins. It doesn't give you any starting CSS.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]ohnojono 1 puan 13 saat önce
Nah, they’re both kinda terrible but you shouldn’t be ashamed 😆
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]big_hilo_haole 1 puan 13 saat önce
What? No, and it's crazy to me that people will make statements like this. If you have your foundation knowledge of CSS then it doesn't matter what flavor of abstraction you use.
This industry is lost. Sad that many of you are too young too know that some of us did this for the fun and excitement of building things and not just a paycheck.
I get some of you have no idea what CSS zen garden is.
Google it, was a time when we had to show web developers that css was powerful, way before abstraction and frameworks.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]intertubeluber 1 puan 13 saat önce
It’s a story as old as time: a new library is released and every internet evangelist jumps on board to promote it. Everyone on Reddit says it’s the best thing ever. Anyone not using it is ethically compromised. Six months later people have used it on real projects and found its not all sunshine and unicorns. Repeat. I’ve skipped so much nonsense by just picking the mature option for my projects.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]TruePadawan 1 puan 12 saat önce
Yes
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]SimonFromBath 1 puan 12 saat önce
I admit I'm old school. But having been a front end dev since before time it feels like, Tailwind misses the point of the initial C in CSS.
I know I'll be called boomer (which I am a few years too young for) but I enjoy what I do and I will personally never willingly use Tailwind.
Saying that. As also a Vue/Nuxt dev, where I build a lot of custom components I can see the use case and reason for its use.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]tristanAG 1 puan 12 saat önce
Who cares, do your thing, there’s no rules
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]lincolncenter2021 1 puan 12 saat önce
Tailwind was made for people who don’t want to learn CSS, suitable for early startups who don’t want to deal with CSS and know nothing about it
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]kaiju505 1 puan 12 saat önce
Idk probably not, I mean tailwind is ok but scss is pretty good. I liked bootstrap better back in the day because it was cleaner but I don’t do a lot of front end these days so my opinion probably isn’t super valid.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]silent-onomatopoeia 1 puan 12 saat önce
Tailwind is clever. That’s not a compliment.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]trey_tallent 1 puan 11 saat önce
Tools are tools, use whatever helps you get the job done.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]patoezequiel 1 puan 11 saat önce
You should be ashamed of robbing me of the minute I took between reading your post and replying to it.
Both are fine, plain CSS is even better.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]BlueKnight3108 1 puan 11 saat önce
The only reason I like tailwind is because I write a bit less, I use it like css files with the apply and I use a line per device size.
First sm Second MD Thirds LG,
So I have something like
.class @apply styles...; @apply md:styles;
And before tailwind I like scss because of the nest
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]FertilityFoes 1 puan 10 saat önce
Utility classes are shit and make code harder to read. SCSS is much better.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]da_bean_counter 1 puan 10 saat önce
My job has tailwind as a requirement and I get PRs rejected if I don’t use it for something that they think can be achieved on tailwind 🥲 also like no JavaScript
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]DioBranDoggo 1 puan 10 saat önce
It’s good but you shouldn’t feel bad because you use say Laravel over Go and HTMX. Use whatever solves your problem.
Like my friend hesitated to move from jquery to react (but switched eventually) because he is more well versed to it. So you do you, solve a client’s problem, and get that bag. I also question tailwind at first but after some tinkering, i find it fun.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]spleenfeast 1 puan 10 saat önce
SCSS is great, even CSS has come a long way and can manage so many things it couldn't before. Tailwind and all the other template frameworks always come and go, I've never bothered with them.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]pobbly 1 puan 9 saat önce
I like plain CSS more than Tailwind. Modern CSS has a lot of what made SCSS popular in the first place (variables, nesting).
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]HollandJim 1 puan 9 saat önce
Absolutely not. It’s like saying you prefer to walk without crutches.
If you can do css without framworks, IMHO, you’re already a better css dev than many I’ve interviewed for jobs in the past 5 years.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Only_Ad2489 1 puan 9 saat önce
What a weird post you are obviously very new to this
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]JimMixedWithDwight 1 puan 9 saat önce
I use TW a lot more now cos I still haven’t mastered BEM TBH. And also my previous job used only tailwind for styling. They wouldn’t even allow me write vanilla CSS so I sorta kinda got used to writing it 😂
But then again I write TW mixed with vanilla CSS all the time, sometimes TW classes gets too long for me and I just use @apply on a declared class and just go with it.
I loved SCSS though but been awhile I wrote it and also CSS has a bunch of new stuff now so SCSS is kinda fading for me.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]eballeste 1 puan 8 saat önce*
hell's fucking no, sass is glorious, I love it and I love that css is starting to adopt sass-like behaviors like nesting. soon I won't need sass but until then, I'm a faithful devotee and hate broken up inline styles with a passion
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]nhonx 1 puan 8 saat önce
Think about when you need to implement Styles for animation, complex selector,...and have to use Tailwind for those things.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Better-Avocado-8818 1 puan 7 saat önce
No
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]wildrabbit12 1 puan 7 saat önce
No, why?
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]librewolf 1 puan 7 saat önce
what the fuck?
even if tailwind wasnt ugly, why would you put yourself down mentally like this?
On the contrary, SASS is fucking beautiful! It gives you the zen styling and it just makes sense.
No ugly fat DOM, heavy duty being done before it reaches the user, and its just a nice DX
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Necessary_Pomelo_470 1 puan 6 saat önce
yes!
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]hoorahforsnakes 1 puan 5 saat önce
As with everything, they are all just tools, and you choose what's right for your situation. Tailwind is useful for maintaining consistancy across a large team of varying ability and enforcing adherance to a style guide, but it also has it's downsides.
Scss has a lot of powerful features (although since it's introduction, a lot have now been introduced to css as standard, like variables, for example, so it's less of an upgrade now)
Personally i prefer postcss over scss, but it's much of a muchness. As long as you aren't being hamstrung by your tooling choices, go with what you feel comfortable with
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]zenotdsFrontend Developer 1 puan 5 saat önce
I’m a SCSS dude as well. I used to hate Tailwind but i admit I’m starting to get its appeal and I’m using it mixed with other stuff in almost every project. That said I can’t wait for it to crash and burn and for everyone to go back to sustainable code.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]MadShallTear 1 puan 5 saat önce
if you love scss is even better..
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]ohlawdhecodin 1 puan 4 saat önce
If you call yourself "developer" but you're unable to understand and code vanilla CSS then yes, you should be ashamed of yourself.
In any other case: you're just using a tool.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]balaasoni 1 puan 3 saat önce
I saw that you can now do nesting in plain css. I tried it and it works great. Doesn’t that take away the need of pre processors like SCSS??
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]imahh17 1 puan 3 saat önce
SCSS for the win, my dude
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]TheComfyDragon 1 puan 2 saat önce
Wtf are you on about? Be ashamed that this thought even cam to your head, when did we have factions in this field? This has to be bot spam
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]neotorama 1 puan bir saat önce
Why not both
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Milky_Finger 1 puan 31 dakika önce
I am just imagining groups of frontend bros in the office bullying eachother based on their preprocessor.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Yhcti 1 puan 15 saat önce
No, you should be proud. Tailwind feels horrible.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]OiaOrca 1 puan 16 saat önce
Both are great! Nothing wrong with having a preference!
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Enough-Can-9162 1 puan 16 saat önce
It’s important to choose the right instrument for the problem, but not a “silver bullet”
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]massiveTimeWaster 1 puan 15 saat önce
They both have their place. Figure out the strengths and weaknesses of both and use them when appropriate. Different tools in the toolbox.
Tailwind is the current CSS darling, that's all. There's always something new coming in a year or two.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]modsuperstar 1 puan 15 saat önce
The word you’re looking for is proud. SCSS is a path toward writing clean nested CSS in the future. I’d say the time for nested CSS is now, but my attempt to try it for a recent project kinda fell apart pretty quickly. Making a media player to use in the browser when you want it to be able to work on old iPads made going full on nested CSS impossible.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]Powershow_Games[S] 2 puan 14 saat önce
I agree it's so nice. I love mixins
kalıcı bağlantıembedkaydetüst yorumgammazlayanıtla
[–]da-kicks-87 0 puan 14 saat önce
SCSS is not a framework , Tailwind is.
kalıcı bağlantıembedkaydetgammazlayanıtla
[–]prettyfuzzy -2 puan 14 saat önce
Yes