> but Emotion to CSS Modules is more relevant to my point. And has nothing to do with Tailwind, Bootstrap, or MUI > But what I'm getting at with the example

> but Emotion to CSS Modules is more relevant to my point. And has nothing to do with Tailwind, Bootstrap, or MUI > But what I'm getting at with the example of Emotion to CSS Modules, is that they both use standard CSS So does Tailwind > Whereas with Tailwind, the utility classes are only meaningful as long as you're fully plugged into the Tailwind ecosystem. Same with MUI. Again, it's much harder to migrate off MUI because it literally binds you to a very specific way to structure your components and other components inside those components. Hell, you can't even move from MUI version X to MUI version X+1 without half of your site breaking. You want to move away from Tailwind to something else? Bring in that something else and use it alongside while you replace your components written with Tailwind classes with that something else. Because Tailwind is literally just CSS.