You might ask why ?
Let me give you a simple example:
Say a developer is creating a button that increases in width by 3% on hover, with smooth transition. Right now, most designers/UI devs would just slap on framer-motion without thinking, which increases the load and build time of that component. But it could be done using just default Tailwind classes.
Now in the case of AI platforms if they have the option to use motion vs raw Tailwind classes, they will (or should) take the Tailwind route. Why? Because these AI companies rent a lot of GPU to render the UI, and using framer-motion will costs more than just using plain Tailwind bcs more build time equal to more money spent on gpu.
And the positive side effect of this?
We’ll start seeing more optimized code. And since a lot of devs are lazy (let’s be real), they’ll directly paste whatever they get from the platform. So that’s a good side effect.