Why I prefer CUBE-CSS instead of Tailwind or Bootstrap or ...

When you take the time to set up a project, Cube CSS offers much more flexibility and control than off-the-shelf frameworks such as Tailwind or Bootstrap. While these frameworks are convenient for quick implementation, they bring limitations as a project grows and requires specific customizations.

For me, building a web application or website is not only about functionality, but also about the fun of the process. I often miss that fun when working with Tailwind or Bootstrap. However, when you set up your own CSS structure, using BEM and Cube CSS, for example, you experience a sense of accomplishment and control. It's almost magical how everything falls into place and you really make your project your own.

Cube CSS is all about creating modular, reusable components that effortlessly adapt to the unique requirements of your project. By using the principles of Composition, Utilities, Block and Exceptions, you not only improve the consistency of your CSS, but also make it easier to maintain. Unlike utility-first frameworks like Tailwind, where styles are often placed directly in the HTML, Cube CSS separates structure and style more clearly. This not only makes your code more scalable, but also more manageable and maintainable in the long run.

From my own experience, I know that working with Cube CSS takes no more time than working with a framework, provided you have a good understanding of CSS. However, that is not a given for everyone. Tailwind feels to me like a reinvention of CSS with the disadvantage that it sometimes becomes cluttered. Everything as a utility is also not pleasant. In contrast, when you write your own utilities and layout classes, you code only what is really needed. This keeps your code organized and manageable.

Because CSS is complete, convenient and fun I prefer a combination of BEM and Cube CSS. It provides structure, clarity and, above all, fun in building websites and applications.