Tailwind css is just crap

TL;DR

Tailwind CSS may seem overwhelming at first with its excessive use of classes, but after exploring and understanding its developer-friendly approach, it can provide a sensible and deliberate experience for writing components.

Transcript

Tailwind is just worst of the worst absolutely bad a really bad nightmare developers should not be using Kelvin this is exactly the thought that you will get when the first time you will open up the Tailwind documentation or you'll try to see or just go through with the documentation of any project that is being built in the Tailwind this was exact... Read More

Key Insights

• 😒 Tailwind CSS may seem overwhelming at first, with its extensive use of classes, but it offers a deliberate and intentional approach to writing CSS. (25 words)
• ☄️ Coming from a background of using frameworks like Bootstrap, developers may initially find Tailwind CSS challenging to grasp, but the developer experience it provides can outweigh the learning curve. (36 words)
• 📽️ Using Tailwind CSS can result in more manageable and scalable projects, as seen in larger-scale projects built with the framework. (23 words)
• 🏛️ While Tailwind CSS isn't the only option for building components, it offers a unique approach that developers should consider exploring. (20 words)
• 🤗 The speaker is open to creating beginner-level Tailwind CSS tutorials or crash courses to help others understand and use the framework more effectively. (24 words)
• 🔇 The speaker's positive viewpoint on Tailwind CSS is influenced by their understanding of its developer experience and the potential for further enhancements in the future. (29 words)
• 😒 The excessive use of classes in Tailwind CSS is not inline CSS; rather, it provides API-level access to generate compiled and production-ready CSS. (29 words)

Questions & Answers

Q: What was the speaker's initial impression of Tailwind CSS?

The speaker thought that Tailwind CSS was the worst way of writing CSS and that it was overwhelming with an excessive amount of classes.

Q: How did the speaker's background in using frameworks like Bootstrap influence their perception of Tailwind CSS initially?

The speaker was accustomed to using pre-built components from frameworks like Bootstrap and only adding minimal custom CSS when necessary. This made the excessive use of classes in Tailwind CSS seem unnecessary and time-consuming to learn.

Q: What changed the speaker's opinion about Tailwind CSS after exploring it further?

The developer experience offered by Tailwind CSS was a key factor that changed the speaker's opinion. After a few days of using the framework, they realized that they could understand and use the classes intuitively without constantly referring to the documentation.

Q: Should developers consider using Tailwind CSS?

Yes, the speaker believes that developers should spend more time using Tailwind CSS. While they acknowledge that other component libraries and frameworks like Bootstrap have their merits, writing CSS in the Tailwind way can provide a deliberate and manageable experience for building components.

Summary & Key Takeaways

• The speaker initially had a negative impression of Tailwind CSS, considering it to be a nightmare for developers and a bad way of writing CSS.

• Coming from a background of using frameworks like Bootstrap, the speaker was used to simply grabbing ready-made components and adding minimal custom CSS.

• However, after delving deeper into Tailwind CSS and exploring its documentation, the speaker realized that the framework offers a different approach to building components with a focus on developer experience.