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…

Tailwind CSS

Tailwind CSS resources and tutorial.

treciaks.hashnode.dev
10
28
3
144
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.
1
2
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!
3
1
2
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.
2
1
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.
1
2
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.
2
1
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.
3
1
And again, we run into the issue of acceleration over potential. It's not the best way to approach big, changing projects and limits innovation imo... A big part of why I think abstraction is the fallback... We do it more than worry about long-term goals and flexibility...
1
Replying to @mholzschlag @dutchcelt @TreciaKS
While we might win time, we lose the web's distribution of language, which yes, does take time, and devolves common skill sets. If I came in to the project and there's a lack of comments, documentation or potential for discovery. Framework is very concrete to me, less flexible.

Oct 23, 2021 · 1:28 PM UTC

1
Replying to @mholzschlag @TreciaKS
Projects with a short shelf life, like promotional websites, are ideal for libraries and frameworks with predefined UI's. Here today, gone tomorrow. Many seem to forget this approach is toxic to large and long-lived solutions.
1
1
The first rule of logic is that there is no logic 😂web sites were not meant to be short term solutions! A web site is not that, really..frameworks to me usually inhibit, not empower. What about interop? Accessibility? Portability? Using APIs purposefully adds abstraction.