The advantages provided by Atomic CSS are extensive and reusable, but they still belong to libraries that in turn rely heavily on javascript to render HTML and classes. Also, some like Tailwind have made the big mistake of not making versions compatible (Tailwind 1 is not compatible with 2). Instead, vanilla CCS maintains its state without incompatibilities. As time passes, what we will have is more of an extended CSS with new attributes that will not break existing ones.
Another thing, writing Tailwind or writing vanilla CSS is just as productive or unproductive depending on one's perception, because writing Tailwind is just as unproductive as writing the hated styles.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The advantages provided by Atomic CSS are extensive and reusable, but they still belong to libraries that in turn rely heavily on javascript to render HTML and classes. Also, some like Tailwind have made the big mistake of not making versions compatible (Tailwind 1 is not compatible with 2). Instead, vanilla CCS maintains its state without incompatibilities. As time passes, what we will have is more of an extended CSS with new attributes that will not break existing ones.
Another thing, writing Tailwind or writing vanilla CSS is just as productive or unproductive depending on one's perception, because writing Tailwind is just as unproductive as writing the hated styles.