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

Programmer Humor

24662 readers
523 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
you are viewing a single comment's thread
view the rest of the comments
[–] expr@programming.dev 9 points 1 day ago (2 children)

I'm honestly not sure, but I'm fairly certain it's intentional obfuscation done for the production build. Why they think it's so important to hide class names, I'll never know.

[–] yumyampie@lemmynsfw.com 4 points 21 hours 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
[–] kautau@lemmy.world 6 points 1 day ago

To fight ad blockers