Tailwind CSS... new generation... Same mistake

I love Tailwind CSS, (It is ironic, I hate it). This statement reflects a personal paradox where the appeal of Tailwind CSS is acknowledged, yet its significance is downplayed. It’s a way to express that while the framework is trendy and useful to many, it doesn’t hold much importance in my view.

All this is my personal point of view only. This article is purely a reflection of my experiences and opinions. It’s essential to understand that these thoughts are subjective and not meant to be universal truths. Each developer may have a different perspective based on their journey and experiences.

I do not complain because coding is a circle of events. In the world of programming, trends and practices often come full circle. What seems new and revolutionary today might just be a reinvention of an old idea. This cyclical nature of development is a familiar phenomenon to seasoned developers.

I am a fan of CSS Zen Garden because it embraced what CSS is really made for. CSS Zen Garden showcased the true potential of CSS by demonstrating how the same HTML structure could be styled in countless visually appealing ways. It highlighted the power and flexibility of CSS, inspiring many developers.

On the 2000's, we were doing layout with tables. This method involved using HTML tables to structure web pages, a practice that was far from ideal. It was a workaround due to the limitations of early web technologies. This period marked a significant phase in web development history.

Then we thought the best way to do CSS was in a semantic way. The industry shifted towards using CSS in a more meaningful manner, aligning styles with the purpose and meaning of elements. This approach was intended to make web development more logical and maintainable.

It was so sexy and seducing to add instructions into classes. Adding styling instructions directly into class names felt innovative and streamlined. It allowed for a clearer structure and organization of CSS rules, making the codebase more intuitive at first glance.

We then understood CSS with all its power and used it the way it was made for. It became clear that using CSS declarations in a semantic manner was not optimized. The tight coupling between HTML and CSS impacted both design and code maintenance. Changes in design could inadvertently affect the code, which was already tested and covered.

Now the time has passed and two generations of developers too. The industry has evolved significantly, and new generations of developers have brought fresh perspectives and ideas. This passage of time has led to the re-evaluation and re-invention of past concepts.

We have this full cycle again, and here we go, Tailwind is revolutionizing all with a brand new approach: semantic CSS. Tailwind CSS is seen as a revolutionary tool, reintroducing the concept of semantic CSS with a modern twist. This approach appeals to many, especially newcomers to the field.

It is the best way for bootcampers to feel seduced. Tailwind’s approach is particularly attractive to those new to web development. It provides a straightforward and effective way to style websites, making it easier for beginners to create visually appealing designs quickly.

Yes, seniors like me, who were there during all parts of the history of the last 20 years, are witnesses. Experienced developers have seen the industry evolve and have witnessed many trends come and go. This historical perspective allows them to understand the recurring nature of certain ideas.

But does it really matter? I don't think so. Why? First, there is a place for everyone. Each developer, regardless of their experience level, has a unique role and perspective. The diversity of thought and approach is what drives innovation in the industry.

Second, as experts, we don't really care about these details anymore. If the past was forgotten so deeply that we think Tailwind is a revolution instead of a recycled idea, it is our fault. Experts have moved beyond debating the merits of specific tools. If the industry repeats past mistakes, it’s a collective oversight.

Third, we are focusing on other things, so let it be the way it should be. We all have the right to go through the development path in the way we feel comfortable. Each developer should be allowed to choose their tools and methods. It’s important to respect individual choices and learning processes.

At the end, yes, I give my opinion, but the real conclusion is everyone should respect others and stop trying to make them change, directly or indirectly. The key takeaway is respect for differing viewpoints. Developers should focus on collaboration rather than trying to impose their opinions on others.

As a conclusion, who cares that Tailwind screws up the code? No one really knows what TDD or unit testing means anymore. There’s no coverage of these pages anyway.