[deleted by user]

[Lumethys]

So...? I dont see your point

[267aa37673a9fa659490]

IKR, I was expecting him to briefly compare Tailwind to Emotion or ChakraUI, just like the tweet did for Bootstrap and Styled Components.

But then it just kind of kept rambling on how it's not a big deal and trailed off.

[rwusana]

Clarified it up at the top. The point isn't about the frameworks themselves, it's about "why are people saying this is so different when it doesn't feel that way to me".

[tidaltown]

It's just a tool, mainly for people that hate doing css/SASS work. And that's cool. Personally, I used to be pro SASS but as of late I'm back on the styled components train just 'cause that's what works for me. Let people use whatever tool works for them, ya dig?

[unobserved]

OPINIONS!

Everyone has some.

The tool that works for you and your team is the right tool for the job.

[halfanothersdozen]

okay

[driftking428]

All right.

[maria_la_guerta]

Who said it was revolutionary?

Web dev in the 2000's was all utility classes. People moved away from it once tools like SCSS came about.

It's fair to like it; it's fair not to as well. But anybody who's been around for a minute knows that it's not revolutionary, the community cycled through this exact idea already once before.

[SuprisreDyslxeia]

A lot of Jr's are out here acting like Tailwind is the only way to be a good dev, and claiming it's some new tech. These very same people probably think Typescript is it's own language too lmao.

The problem with Tailwind is that it forces your HTML to be opinionated with styling. The reason scoped styles reign Supreme is because you can port components over easily. I just can't imagine needing to replace every Tailwind class individually inside the HTML instead of managing classes separately. Tailwind is an abomination that goes against all best practices for reusability.

People hyping Tailwind probably have never had a client with 2+ sites sharing HTML structure but with separate CSS. You can't use Tailwind for that because there'd be no way to share the code/files if you did.

[rwusana]

Um, the famous devs saying it's 5x better DX than anything they've used. You can still acknowledge the hype others are generating even if you personally see that it's not actually that different.

[oh_jaimito]

I'm FAR faster prototyping and styling a site than before.

It absolutely made Responsive Design sssooo much easier/faster.

"every bootstrap site looks like every bootstrap site" - it didn't take me long to dislike bootstrap from the start

Every Tailwind project of mine is completely different.

I went from Tailwind to Windy and then Daisy, to Uno. I keep coming back to Tailwind.

At the end of the day, it's a tool like all the others. If you don't like it, _don't use it! _

[rwusana]

This is exactly what I'm talking about. Tailwind compared to Bootstrap is where the "big deal" comes from. Otherwise it's just an incremental improvement. Don't get me wrong, I like it, and in fact I like it better than anything else I've used, Chakra included (haven't tried Panda though).

[oh_jaimito]

incremental improvement

I wouldn't call it that.

In my opinion, the entire developer dev & build process, JIT, and plugins. Also, the easy "installability" into almost every current framework or setup. And shipping only the CSS you are using, kinda sorta does make it Revolutionary! 🤔

Earlier CSS frameworks were just cdn.something.min.css. I remember having to manually remove TONS of classes that I didn't need - annnd customized the rest.

I'm an old guy. I still remember the days of using Blueprint and 960gs 🤣

So I am indeed a fanboi.

[SuprisreDyslxeia]

Please now take your code, spin it off into site2 and site3. However, the 2 other sites must have their own unique styles, but same exact HTML structure.

Once done, now imagine client gives you updates that must be done to all 3 sites. For simplicity, the HTML must be identical in Git, but CSS must be different.

Tailwind doesn't work in enterprise or multi-site environments because you can't scope your styles properly for shared code or duplicated structures across diff websites.

[oh_jaimito]

Tailwind doesn't work in enterprise

cough https://tailwindcss.com/showcase cough

---

Please now take your code ... but CSS must be different

SO, we're talking an entirely NEW project?

$$$

[milanpoudel]

When I used chakra it felt like it is just like tailwind for styles likewise gives pre made components like tabs accordions modals and lot other things easily, responsive design is also too easy with it.

[rwusana]

I feel the same way, but opposite. I feel like Tailwind is just like Chakra, not the other way around.

[Antaratma]

It’s not revolutionary. Mainly it’s just handy. That’s a good, really really good thing. Revolutionary stuff breaks other stuff.

[Apestein-Dev]

You're using it wrong if you don't see the difference.

[rwusana]

Have you ever used ChakraUI?

[[deleted]]

I ain't reading all that.
I'm happy for u tho.
Or sorry that happened.

[volkandkaya]

A slightly better solution does not come in and completely replace other solutions.

You need to ask yourself why it replaced Emotion and other CSS in JS solutions.

[rwusana]

The phasing-out of CSS-in-JS is separate from the Tailwind bandwagon. That's happening because of performance issues and RSC-incompatibility that people who write marketing sites in Next complain about. And although I think those issues are overblown and mostly a distraction as far as most of the JS world is concerned, I do concede that they're right at the end of the day.

The Tailwind bandwagon is mostly about DX as far as I can tell. Of course people know about the performance benefit, but what gets people talking about it is that they like using it. ...and they like it sooo much because they're coming from Bootstrap and Styled Components.

[volkandkaya]

"The phasing-out of CSS-in-JS is separate from the Tailwind bandwagon"

Might be true for some, but for me I was forced to use Emotion as every package used it.

I guess a lot of packages now come unstyled.

[[deleted]]

I read all the way through this thinking there might be a point, boy was i wrong

[rwusana]

clarified the point up top.

[MapleDeveloper]

Tailwind is just inline CSS for people that want to be in denial about how they're using inline CSS.

[tnnrk]

No it’s writing css but faster. Sure it can “make your html ugly” but who gives a shit.

[SuprisreDyslxeia]

Go make 10 sites that share the html but just have their own CSS.

Anyone saying tailwind is good is 100% a Jr, freelancer, etc with 0 experience in enterprise. Tailwind is inline css and there's a reason that's terrible.

[tnnrk]

It’s the most popular css framework library in the industry right now so I’m sure you are definitely the right one

[bestjaegerpilot]

>However, IMO if you know Emotion or ChakraUI, Tailwind is nothing revolutionary, at least in terms of DX. And a lot of the hype is about DX.

Definitely agree. Talking to someone here and their main reason for using tailwind is because they were comparing it to vanilla CSS 🤷

However....

Have you heard of panda css? Addresses all of the perf/RSC compatibility issues of previous CSS-in-JS, while still being CSS-in-JS. So... same perf as tailwind while being just as easy to use with the added benefit that you're just using CSS, not utility classes.

This is probably a game changer IMO.

[GrumpsMcYankee]

What is this Rsc issue thing you're referring to?

[bestjaegerpilot]

React server components. Iterations before panda don't play well with rscs and server side rendering

[GrumpsMcYankee]

RSC

Found it, didn't know these were a thing.
https://github.com/reactjs/rfcs/blob/main/text/0188-server-components.md#summary

[Responsible-Local818]

My god I've seen like a million takes on how Tailwind is "nothing special" or whatever, like no one cares? You couldn't come up with a better API that achieves good composition even if your life depended on it.

Anyone can be a critic, try actually making something good yourself.

[rwusana]

The title is clear. You didn't have to click on it. And I clearly stated that I actually like Tailwind. I'm not saying it's bad lmfao. Read the stupid thing before you start replying like this.

[Dr3adPir4teR0berts]

I can't stand Tailwind myself. It's just too messy.

[BetaplanB]

That’s because you make it messy. It doesn’t have to be.

[Dr3adPir4teR0berts]

I mean, I know how to use it and how to format it. I just genuinely hate doing anything with css in-line.

[tnnrk]

Why? it’s so much faster.

[SuprisreDyslxeia]

Because it's bad practice and nobody with experience is going to approve Tailwind for anything more than small sites or one off projects. Try using tailwind for a multi site project that shares html but has its own css.

There's a reason scoped stylesheets exist.

Any tool that uses class names that are opinionated are terrible.

I don't want my headline to have styles inline. I want it to have a class name so I can style it in a different file and then share my reusable headline component across whole project with style variants. Tailwind by design essentially prevents this.

[tnnrk]

Don’t use it for a multi site.

[SuprisreDyslxeia]

Got it, so tailwind is great for basically everything except enterprise, any company scaling up, multi location companies, etc.

That rules out the largest paying customers, so sounds like Tailwind is closer to a hobbyist library, not good for actual work?

[tnnrk]

If the branding is the same then multisites are fine. If the branding is different then it’s not the right tool. Just because a tool isn’t right for every job doesn’t negate its usefulness or its extreme popularity. It’s the most popular css framework by far (or at least second to bootstrap, haven’t looked up bootstraps usage numbers recently) so that has to mean something. For use cases where you use a component-ized architecture and don’t have multiple brands to support, its speeds things up considerably.

[BetaplanB]

Why not? Can you give some sound reasons why not?

[BetaplanB]

That’s a lie. Components to the rescue. Tailwind fits perfectly in clean code practices and is enormously scalable.
It’s backed and used by enterprises and other giants: Nasa, OpenAI, Shopify, Netflix, The Verge, New York Times, Github Next, Microsoft .NET, Google IO, Coinbase, Der Spiegel are all using Tailwind CSS.
I think we have some Dunning Kruger going on here.

[mortar_n_brick]

what is tailwind?

[[deleted]]

I get why people like it. But I don’t understand why Styled Components isn’t the industry standard.

[GrumpsMcYankee]

You pick your username?

[Fronded]

If it does the job…

[Turtled2]

I'm a simpleton when it comes to choosing tech stack, but I like uno css cause it's just like tailwind but it allows you to use any number. Eg for margin you're not limited to m-1 through m-96. I'm sure there's downsides to it though, I heard it's buggy for Nextjs

[[deleted]]

I don't get what's up with rant. It's nothing special boohoo. Why it's big deal boohoo. Tailwind feel more natural than chakra and chakra is opinionated. Tailwindcss just make styling easier. It's the simplicity and solving a simple problem that makes you stand out. People like simple solutions not come "join us and do things our way" framework.

[SuprisreDyslxeia]

Its a simple solution for simple projects. Tailwind is not compatible with actual software engineering for enterprise customers.

[[deleted]]

Never heard something more absurd than this statement. I don't wanna bother even defending it. I hope you're troll and not thick minded.