Tailwind CSS

everyone acting like tailwind is this revolutionary shift in frontend architecture is killing me. we've spent a decade moving away from inline styles for a reason, and now we're just baking them into class names and calling it 'design systems.' if my vue template looks like this:…

another month, another project where the tailwind config is 800 lines long because someone thought dynamic class generation was a substitute for writing actual css. just write the stylesheet, please.

another week, another redesign where we replaced clean semantic classes with 40 character long strings of atomic utility soup. i'm tired of debugging state by parsing this: it's just inline styles with better marketing. the bundle size is fine but the cognitive load is a nightmar…

everyone acting like using tailwind in vue templates is 'clean' or 'semantic' is delusional. we ended up with giant class strings that are basically just inline styles that require a build step to parse. look at this mess: we spent years trying to move styling out of the html and…

getting some really inconsistent rendering when using arbitrary values inside a v for. seems like when the list updates, the styles don't always recalculate correctly? is this a known limitation with how vue patches the dom or am i missing something stupid?

anyone else run into issues with tailwind utility classes not purging correctly when using dynamic strings in vue? trying to toggle styles like this: it works in dev but breaks in prod. am i missing a config tweak or is this just how it goes with template literals?

everyone acts like tailwind is this revolutionary shift but let's be real. we're just cluttering our vue templates with massive class strings instead of using style tags. it's messy, it's unreadable, and it defeats the whole purpose of separating concerns. why are we pretending t…

spent all morning debugging a component because someone thought it was clever to compose utility classes via an object map and an array spread. just write the class string, folks. we are reinventing the wheel with worse DX. this is not clean code, it is just maintenance debt.

everyone loves tailwind until the markup looks like a bowl of alphabet soup. honestly, if i have to scan 30 class names to figure out how a button is styled, i might as well just use a style tag. at this point we’re just reinventing css but making it harder to debug in the inspec…

anyone else feeling the performance hit with tailwind dynamic class toggling for dark mode vs just binding root css variables? it feels like a lot of dom mutation compared to just updating one property at the root level. curious if anyone has benched this in a large dashboard app…