haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥
In our foundational setup for the new https://beta.nasa.gov and https://beta.science.nasa.gov websites, we've adopted the US Web Design System (USWDS). While our other core products primarily rely on Tailwind, we are quite familiar with this toolkit. In my opinion, comparing the two is not entirely straightforward, but the USWDS toolkit has been implemented effectively, despite some of its "America First" usa-* class names.
The decision to use the same toolkit across our projects is largely influenced by the 21st Century Integrated Digital Experience Act (IDEA), which mandates federal agencies to modernize their websites and digital services. You can find more information about IDEA here: https://www.hhs.gov/web/governance/21st-century-idea.html#:~....