| ▲ | Lalabadie a day ago | |
What component-specific styles look like: class="menu-item" Styles-in-HTML (Tailwind): class="m-4 mb-2 p-2 border border-radius-sm border gray-200 hover:border-gray-300 font-sm sm:font-xs [...]" You can be completely insensitive to or unbothered by the difference, but that doesn't mean they're equivalent. | ||
| ▲ | Klonoar 12 hours ago | parent [-] | |
I'm not saying they're equivalent. I'm saying that the latter is better, especially in the context of reviewing LLM output. With the former, I need to cross-reference two different stacks (HTML and CSS) and construct a mental model every time I move between components. With the latter, I can simply look at one output (HTML) and move on with my life, knowing that the chances of conflicts/issues/etc are fairly limited. You guys are advocating for keeping the semantic separation that we originally aimed for with HTML/CSS, but in an LLM world this is yet another distinction that probably "does not matter". | ||