(tailwindcss.com)

159 points creativedg | 1 comments | 22 Nov 24 02:12 UTC | HN request time: 0.207s | source

Show context

that_guy_iain ◴[22 Nov 24 03:55 UTC] 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. emmanueloga_ ◴[22 Nov 24 05:58 UTC] No.42211498[source]▶

>>42211038 #

I think the rewrite aimed to simplify installation and configuration. TW 4.0 switched from PostCSS to LightningCSS [1], and Rust-based tools tend to offer a simpler setup via single binaries (in contrast to the complexity of typical JS-based tools).

Moving from pure JS to Rust also brings performance gains. Even if the main goal wasn't "performance," it's a nice side effect worth highlighting.

1: https://lightningcss.dev/

↑

Tailwind CSS v4.0 Beta 1