Tailwind CSS! Ever wondered what it was? How is it different from Boostrap or what makes it better? Learn what utility classes are and how they can possibly make you never go Vanilla CSS again, learning resources provided! treciaks.hashnode.dev/tailin…

What I get from this is that it is all about the selectors. Structuring your CSS is an important part of the work. If Tailwind fits that’s great. For a design engineer it’s one of many approaches that’s nice to have at your disposal.

Hi Egor long time! Can you explain to me a used case or two I'm getting so sick of Frameworks I swear I will throw myself off a building if another one comes out CSS or JavaScript or anything else it's just a personal pain at this point I'd be interested in your thoughts!

This requires a long answer, maybe even worth an article. The impressive thing about Tailwind is that it found away to use the utility class name approach for everything. However, no matter the project over the years I haven’t been able to use it. It’s use case is rather narrow.

The 'styling' problem isn't libraries like Bootstrap or Tailwind it has more to do with how they're implemented. Writing CSS in a structured way and abstracting it away from the markup is what class attributes are good at. Tailwind has done away with that decoupled approach.

Tailwind, and Bootstrap to a lesser degree, have integrated their API, utility class attributes, with the markup. If you don't own the markup then you end up writing a custom abstraction. Adding hard to manage complexity.

If you create stand-alone applications or websites and don't share or reuse code with other web stacks then using Tailwind in such cases accelerates development and reduces knowledge and skill pressure from the team.

I can agree that having the tools That are most appropriate and efficient for a given project makes absolute sense. But knowing to use or not to use a given approach,can cause even more confusion when teaching and learning how 🤗