That's a bit of an unfair straw man... Tailwind CSS is not meant to be used via CDN—it should always be used as part of a build process. One of the main pros for choosing to use Tailwind CSS is its tiny production build file size, as attested on their homepage: tailwindcss.com/#performance.
Yes, that's why I said "Tailwind is best used as a PostCSS plugin, or as part of the JS build process" .. I think the article should mention this in comparing the two.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That's a bit of an unfair straw man... Tailwind CSS is not meant to be used via CDN—it should always be used as part of a build process. One of the main pros for choosing to use Tailwind CSS is its tiny production build file size, as attested on their homepage: tailwindcss.com/#performance.
Yes, that's why I said "Tailwind is best used as a PostCSS plugin, or as part of the JS build process" .. I think the article should mention this in comparing the two.