←back to thread

Tailwind CSS v4.0 Beta 1

(tailwindcss.com)
159 points creativedg | 4 comments | | HN request time: 0.001s | source
Show context
that_guy_iain ◴[] No.42211038[source]
I'm really curious as to why they felt the need to work on improving performance.[1]

Were people complaining it was too slow? Were the performance improvements just the benefit of refactoring they did for other reasons?

Considering the build happens once during your build phase, taking under half a second doesn't seem like something I would even bother looking at. So it just jumps out to me, so I'm just curious.

[1] https://tailwindcss.com/docs/v4-beta#new-high-performance-en...

replies(5): >>42211115 #>>42211179 #>>42211209 #>>42211283 #>>42211498 #
1. dcre ◴[] No.42211209[source]
I think a lot of the optimization work was for dev time and it carried over to build time. I listened to a podcast interview with Adam Wathan where I think he said they just got really into shaving nanoseconds. They have a very successful business and I think they just enjoyed doing this work. On the other hand I do think even if you’re cutting from 50ms to 5ms (both low numbers in absolute terms) there are often new unforeseen workflows that become possible once you can do that operation so frequently that it’s free. You could do it on every keystroke.
replies(1): >>42211423 #
2. joshdavham ◴[] No.42211423[source]
> there are often new unforeseen workflows that become possible once you can do that operation so frequently that it’s free. You could do it on every keystroke.

That’s really interesting to think about actually! What kinds of practical things do you think could be enabled by an extremely fast tailwindcss?

replies(2): >>42211602 #>>42211714 #
3. mattigames ◴[] No.42211602[source]
LLM trying design using tailwind, stuff like: try to recreate this bitmap image using tailwind utility classes; the iteration speed for that kind of tasks depend on such speed.
4. LaundroMat ◴[] No.42211714[source]
Live reloading