Understanding the trade-offs of using Tailwind CSS
1–6 of 6 posts
Re: Understanding the trade-offs of using Tailwind CSS
#2Re: Understanding the trade-offs of using Tailwind CSS
#3When landing on this author's site, I immediately thought it looked like it was made with Tailwind. The lengths they went to create their entire own custom CSS and design system to match the choices that Tailwind makes is interesting.
Re: Understanding the trade-offs of using Tailwind CSS
#4> Potential brand conflicts > > Tailwind makes design choices so designers and developers don't have to. This can result in a recognisable look. Those familiar with Tailwind can often spot Tailwind-built sites. When landing on this author's site, I immediately thought it looked like it was made with Tailwind. The lengths they went to create their entire own custom CSS and design system to match the choices that Tailw…
Re: Understanding the trade-offs of using Tailwind CSS
#5Re: Understanding the trade-offs of using Tailwind CSS
#6But, here's an issue for me: it makes your (cacheable/compressible) CSS smaller and your (uncacheble/uncompressible) HTML larger
Of course, you can cache and compress HTML. Unless you're using TLS, then you should not compress HTML (see BREACH). And unless you have any dynamic data on your page, then you won't be using caching...
And Tailwind makes HTML responses quite a bit larger