this post was submitted on 30 Jun 2025
415 points (97.9% liked)

Programmer Humor

24670 readers
248 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
415
[ComiCSS] Benefits of Tailwind (files.catbox.moe)
submitted 2 days ago* (last edited 2 days ago) by [email protected] to c/[email protected]
77 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 2 days ago

It is not intentional. The tooling needs to generate a short unique id to prevent css name clashing.

During development 2 developers can write the same css class name in two seperate places:

  • developer A: .container { padding: 8px } at dashboard
  • developer B: .container { padding: 32px } at sidebar

Without this tooling developer need to find ways to prevent name clashing:

  • .dashboard__container
  • .sidebar__container

and they need to do this for every class name.

with this tool, developer don't have to worry about this ever, continue using .container and it get generated into:

  • .aP2be7
  • .7aFrJp