Atomizer VS Sass

Tailwind CSS is a CSS framework that has gained incredible popularity, with usage skyrocketing 40% in three years, according to the State of CSS 2022. It offers benefits such as development speed, maintainability, and gzip optimization. As a result, it is expected to exceed 50% in the 2023 survey. However, the readability of Tailwind CSS decreases sharply as the style becomes more complex, which is a typical disadvantage of the utility-first approach. Personally, I recommend my library, CSS Lube, but in this article, I would like to introduce some simple tips that can improve the developer experience when using the Atomic CSS approach.

Dokumentasi resmi ACSS: https://acss.io/

Language - Master is a language, but it was originally inspired by ACSS's concept of atomic classes.

Tailwind and React are two leading technologies in their sphere. Tailwind CSS simplifies the concept of Atomic CSS, enabling developers to style their UI by adding some classes to their markup. And with the performance improvements that come with the new JIT compiler, Tailwind CSS has become a clear developer's favorite.

Atomic frameworks like Atomic CSS and Tailwind takes a single purpose approach to selectors, so CSS properties are naturally never overlapping – this is also why Tailwind's @apply is an anti-pattern when overused.

It sure is ugly-looking but it works well! Drawing inspiration from Atomic CSS and utility classes (1 class = 1 style), Tailwind makes a few strong design decisions:

Atomic CSS is the approach to CSS architecture that favors small, single-purpose classes with names based on visual function.

There are all kinds of approaches people take to maintain clean HTML/CSS, such as BEM or Atomic CSS.

Atomic

SASS(.scss) [ https://sass-lang.com ]

Traditionally CSS lacked features such as variables, nesting, mixins, and functions. This was frustrating for Developers as it often led to CSS quickly becoming complex and cumbersome. In an attempt to make code easier and less repetitive CSS pre-processors were born. You would write CSS in the format the pre-processor understood and, at build time, you'd have some nice CSS. The most common pre-processors these days are Sass, Less, and Stylus. Any examples I give going forward will be about Sass as that's what I'm most familiar with.

CSS stands for Cascading Style Sheets, and is a scripting language used to style web pages. SCSS stands for Syntactically Awesome Style Sheet, and is a superset of CSS. You can think of SCSS as the more advanced version of CSS, which comes with several features that CSS does not support, such as the SCSS nested syntax, as shown below.

Scss

In the past, you’d need to rely on pre-processors such as SaSS or Less, but not anymore… Native CSS nesting has landed on all major modern browsers.

Sass is also a css preprocessor. Op is likely confused

sass -> An improvement over CSS. It provides nice features for managing CSS. good for mid-sized or even larger projects.

Sass (Syntactically Awesome Style Sheets) - A CSS preprocessor that simplifies and enhances your CSS workflow. Website: https://sass-lang.com/

Personally, my preference is Sass: I find that the mixins, partials, and operators are hugely useful when it comes to creating re-usable snippets of code for a design system. And, since it’s “just” a pre-processor and not a framework, it’s not opinionated in a design sense and there’s no default values (colors, spacing values, etc.) that will need to be overwritten.

Preprocessors: SSGs leverage preprocessors to streamline the development process. Preprocessors like SASS for CSS or Babel for JavaScript offer additional features and simplify code development.