That's a great article - really interesting to see Tailwind from the perspective of someone having used it in anger.
I've been using a similar utility-first CSS approach in some of the codebases I work on, but haven't encountered some of the same problems as yourself for width/ height. We usually completely avoid fixed widths or heights though, as both can be problematic for responsiveness (especially on smaller mobiles).
That's a great article - really interesting to see Tailwind from the perspective of someone having used it in anger.
I've been using a similar utility-first CSS approach in some of the codebases I work on, but haven't encountered some of the same problems as yourself for width/ height. We usually completely avoid fixed widths or heights though, as both can be problematic for responsiveness (especially on smaller mobiles).
Really good article though - thanks!
Not necessarily anger, but minor frustrations / things I would fix.
I do tend to stay away from fixed widths, but when they are needed it is that extra step that can be a bit frustrating.
Thanks for the read.