Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tailwind CSS v4.0

tailwindcss.com

Post reply on HN
Print view View original

191–200 of 296 posts

Re: Tailwind CSS v4.0

#191

Post by jmull »

ricw wrote: post #96
jmull wrote: post #61

Earlier quoted context omitted.

> Or should I just reinstall Bootstrap and be done with this. That one. Tailwind gives you tools when you want to control the design, but you’ve got to control the design. When you just want something that looks good and don’t mind that bootstrap-y feel, bootstrap is the way to go. (There are projects that essentially recreate bootstrap on top of tailwind, which, in theory, might give you something like bootstrap as…

Disagree. Just get one of the tailwind UX kits and use their classes as your standard style guide. I personally use flowise as it’s free with paid more complex components if needed, but there are a bunch of others out there that fill the same space.

That's fine (I've done it). It's just that bootstrap is better at it.

Re: Tailwind CSS v4.0

#192

Post by dankobgd »

crummy wrote: post #4
rglullis wrote: post #2

"Build times reduced", "no more @tailwind directives", "No more js configuration", "Designed for the modern web". To me, this screams "CSS now can do everything we used to do ourselves, but let's keep pretending that we are still needed somehow"

What did you need Tailwind for before that you couldn't do in normal CSS? Doesn't Tailwind map pretty much 1:1 to CSS?

It's a horrible way to do what css can do but in a dumber way with added tooling. It is used by people that don't know css and this is where the problems start

Re: Tailwind CSS v4.0

#193

Post by dcre »

silverwind wrote: post #138
dcre wrote: post #93

Earlier quoted context omitted.

That is more or less how it worked in v3 already, because any string could be used as a CSS class. "The way Tailwind scans your source code for classes is intentionally very simple — we don’t actually parse or execute any of your code in the language it’s written in, we just use regular expressions to extract every string that could possibly be a class name." https://v3.tailwindcss.com/docs/content-configuration#clas…

In v3, one can use `blocklist` in the config to eliminate false-positives, but with the config file gone, this seems no longer possible, so I won't be upgrading. In one project, roughly 75% of the detections were false-positives, unnecessarily bloating the CSS.

You can disable automatic detection and manually configure which files to look at:

https://tailwindcss.com/docs/detecting-classes-in-source-fil...

Re: Tailwind CSS v4.0

#194

Post by robjn »

Fred27 wrote: post #167

Tailwind suits the kind of developers who hack things together and build up technical debt and spaghetti code rather thinking about things first and designing things properly.

Hard disagree. Vanilla BEM + CSS produces a parallel component system that I find very unwelcome since React (or Vue/Svelte/etc.) already accomplishes this.

Tailwind removes this burden and helps you focus on writing actual React components when needed.

Re: Tailwind CSS v4.0

#195

Post by dbbk »

agos wrote: post #161
dbbk wrote: post #157

Earlier quoted context omitted.

> I don’t miss the days of emotion and styled components where I would have to think of a name for every styled div in the project I see people mention this issue fairly frequently, and it puzzles me a little. I have never once spent probably more than 1 second thinking about what to name something. Is it actually a blocker for some people? Are you really paralysed by this?

especially since with any decent CSS solution (any css in js, or CSS modules) you can reuse names

Like really, I use Styled Components, just call it a Wrapper or InnerWrapper or Row or whatever and move on

Re: Tailwind CSS v4.0

#196

Post by mablopoule »

skeletal88 wrote: post #147
aembleton wrote: post #145

Earlier quoted context omitted.

> I simply don't see the appeal. - Not having to name CSS classes - Easier to read as it's inline with the rest of your HTML - Standardised way of naming so that everywhere uses the same conventions - Not having to manage a separate file and remove unused components - Being able to use media queries, which I couldn't do in a style tag - No risk of changing a class that is used elsewhere. CSS has global scoping which…

The problem is that with bootstrap I have card, table, etc. With tailwind I have an unreadable alpabet soup when I am not a designer but a developer and am not familiar with tailwind.

This is the big one for me. In any big enough or unfamiliar frontend project, my go-to way to explore the codebase is to launch the front-end, and use the inspector to check the elements, and then search-back in the codebase the relevant classes to see what page/component display that, and how does it fetches the data.

If there is only an alphabet soup, I no longer have a simple set of classes I can grep the codebase with to quickly find the relevant components.

Re: Tailwind CSS v4.0

#197

Post by dbbk »

agos wrote: post #158
4m1rk wrote: post #85

Earlier quoted context omitted.

I just want the color palette of the Tailwind CSS.

yeah, the palette is neat. My main gripe with Tailwind is that it blends a set of design tokens (which I like) with a technology to apply them (which I don't like)

Just copy and paste them out?

Re: Tailwind CSS v4.0

#198

Post by dbbk »

vim-guru wrote: post #119

CSS has become significantly more user-friendly than in the past, with most browsers now behaving consistently. It's worth learning as there is no build step involved, and it avoids cluttering your markup with excessive code. You could opt to use style attributes directly within your HTML. Historically, we avoided this to maintain a separation of concerns, but it's puzzling why some prefer reintroducing similar metho…

You're seriously advocating for inline styles in the year 2025, it does not surprise me you are confused.

Re: Tailwind CSS v4.0

#199

Post by krnsi »

preisschild wrote: post #125
arcanemachiner wrote: post #95

Earlier quoted context omitted.

FWIW Tailwind can be used as a standalone executable. This is how Phoenix/Elixir bundles Tailwind without requiring npm.

AFAIK using the tailwindcss-cli without npm makes it impossible to use Tailwind plugins, such as DaisyUI.

This is not true, here is a demo projects which uses the Hex Tailwind and DaisyUI: https://github.com/naymspace/backpex/tree/develop/demo

Re: Tailwind CSS v4.0

#200

Post by gedy »

jgalt212 wrote: post #176
4m1rk wrote: post #85

Earlier quoted context omitted.

I just want the color palette of the Tailwind CSS.

Yes, someone should make a tailwind inspired bootstrap theme.

I actually did this for a former company that had a Bootstrap-based app - the designers started bugging that "we need to use Tailwind", and I couldn't figure out why they cared what tech we used.

In talking with them, realized they just were bored with our theme, ha. Not publicly accessible though, sorry. I should probably recreate this.

Post reply on HN