Pro@programming.dev to Programmer Humor@programming.devEnglish · edit-23 days ago[ComiCSS] Benefits of Tailwindfiles.catbox.moeimagemessage-square77fedilinkarrow-up1425arrow-down19file-text
arrow-up1416arrow-down1image[ComiCSS] Benefits of Tailwindfiles.catbox.moePro@programming.dev to Programmer Humor@programming.devEnglish · edit-23 days agomessage-square77fedilinkfile-text
minus-squareyumyampie@lemmynsfw.comlinkfedilinkarrow-up5·2 days agoIt 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
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:
.container { padding: 8px }
at dashboard.container { padding: 32px }
at sidebarWithout 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