There's a worrying trend in modern web development, where developers are throwing away decades of carefully wrought systems for a bit of perceived convenience. Tools such as Tailwind CSS seem to be spreading like wildfire, with very few people ever willing to acknowledge the regression they bring to our field. And I'm getting tired of it
Ok so use modern frameworks and tools that implement the tailwind plugin. Because if you are shipping the entire tailwind css that’s a developer problem not tailwinds. News flash: using a technology wrong doesn’t make the tech wrong.
News flash: your snark makes you an unpleasant person. Read my comment again. I said tree shaking fixes this… unless you don’t know what content you’ll display and what classes you’ll need at build time. Not all sites are static.
Unless you are going to be allowing custom html to be added the tooling is smart enough to figure out what possible classes your code can use. You’d have to do something dumb to not have the tools able to tell what components you are serving.
Make an element that is hidden that has all possible values of classes you can use. Or use normal css for that one part of your app if that isn’t possible. Lots of ways you can handle this without thinking the framework doesn’t work.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@beehaw.org
All things programming and coding related. Subcommunity of Technology.
Ok so use modern frameworks and tools that implement the tailwind plugin. Because if you are shipping the entire tailwind css that’s a developer problem not tailwinds. News flash: using a technology wrong doesn’t make the tech wrong.
News flash: your snark makes you an unpleasant person. Read my comment again. I said tree shaking fixes this… unless you don’t know what content you’ll display and what classes you’ll need at build time. Not all sites are static.
Unless you are going to be allowing custom html to be added the tooling is smart enough to figure out what possible classes your code can use. You’d have to do something dumb to not have the tools able to tell what components you are serving.
More generally, the more you have a flexible editor in the app, the worst it gets. This is the use case where I ran into trouble.
Make an element that is hidden that has all possible values of classes you can use. Or use normal css for that one part of your app if that isn’t possible. Lots of ways you can handle this without thinking the framework doesn’t work.
Ninja:
https://tailwindcss.com/docs/content-configuration#safelisting-classes
Tailwind actually has this use case covered already. Use the safe list functionality to always include the classes you need.
The “News Flash” bit was unnecessary. Please keep your replies to other users respectful on Beehaw.
Thanks!
— !programming@beehaw.org Moderation Team