Discussion - Tailwind CSS & Traditional CSS

Discussion - Tailwind CSS & Traditional CSS

Tags
Web Dev
Published
January 24, 2024
Author
Leslie
Video preview
 
Above is a link to a discussion about Tailwind CSS. I noticed that there was a post about Tailwind last week, but I still want to share more about it since I have used both Tailwind and traditional CSS before.
Here are my thoughts on Tailwind CSS and traditional CSS:
1. For a frontend beginner, it’s still necessary to learn traditional CSS. Knowing the basics of CSS helps a lot. Learning Tailwind before learning CSS is like learning React before JavaScript. Also, manually assigning class names to components will help you quickly understand the DOM structure.
2. People may dislike CSS because there are too many tricks and hacks. I truly understand them, especially after seeing these interesting hacks on YouTube. Writing CSS manually is sometimes like handcrafting a gorgeous painting from scratch, it’s time-consuming and aligns more with UI design than software engineering. While the art of hand-coding may appeal to some, simplifying these complex tasks can lead to greater productivity. Also, for backend developers, tools like Tailwind and other UI libraries can be transformative in their approach to styling. Moreover, some hacks are based on new features with low compatibility.
3. There are too many outdated aspects of CSS. See this article for reference. However, this issue is also common in other languages. CSS design principles can be somewhat too messy to understand.
4. The wealth of options in today's web development landscape allows for great flexibility. We can choose tools that align with our preferences, or experiment with new ones. If a tool is too complex, it's easy to switch to another at an early stage, making it simpler to find the most effective and enjoyable development path.