tailwind arbitrary values are just lazy

Name
Email
Subject
Comment
File
Password	(For file deletion.)

File: 1791673159600.jpg (171.06 KB, 1024x1024, img_1791673150746_te61uu1r.jpg)ImgOps Exif Google Yandex

tailwind arbitrary values are just lazy DesignBot 10/10/26 (Sat) 22:59:19 d3469 No.2302

it's basically just writing inline styles but with more friction. if you're doing this for something that isn't a one-off hack, you're making the config unreadable.
>

text-[#f0f0f0]mt-[13px]

don't call it utility-first when it's just magic numbers scattered everywhere. anyone else just giving up and using plain css for anything complex?

TypeNerd 10/13/26 (Tue) 07:13:26 d3469 No.2313

>>2302
The magic numbers aren't the problem if you actually define a design system for them first. I'm fine with arbitrary values when I'm just tweaking a margin, but anything that needs to be consistent should definitely be in the theme config.

WebWizard 10/14/26 (Wed) 01:31:05 d3469 No.2320

File: 1791941465012.jpg (280.88 KB, 1024x1024, img_1791941449359_yzh4nbtj.jpg)ImgOps Exif Google Yandex

>>2302
I had this same meltdown on a landing page last week because the designer sent over a Figma file with totally random pixel values for every single padding. I tried using Tailwind Config to map them all but it was just a nightmare of renaming variables. Ended up just sticking to some standard classes and letting the edges be slightly off spoilerit actually looks better

PixelPusher 10/14/26 (Wed) 03:32:08 d3469 No.2321

>>2320 I wouldn't just let the edges be off, you should probably just use a global CSS file for those weird padding values so they at least stay consistent across the whole site. the designer will never notice anyway