Arguments against twin.macro in favor of TW
Hello all!
At work, I am in the process of making the argument for using normal Tailwind over twin.macro. Our last project used twin but in the next I am trying to push hard for abandoning it in favor of the rational stack of TW, CVA, TW merge and CLSX.
As far as I can tell, there is only downside for the end user when using JSS.
Does anyone have any concrete resources they've created or come across to demonstrate this?
I understand that TW merge can have some runtime effects on initial load, but sure it wouldn't be measurable compared to all the runtime JS in emotion, correct?
Also, I am looking for some articles or material on why "semantic css" is a problem that Tailwind is explicitly designed to solve.
Any points on this topic would be greatly appreciated!
Thanks!
At work, I am in the process of making the argument for using normal Tailwind over twin.macro. Our last project used twin but in the next I am trying to push hard for abandoning it in favor of the rational stack of TW, CVA, TW merge and CLSX.
As far as I can tell, there is only downside for the end user when using JSS.
Does anyone have any concrete resources they've created or come across to demonstrate this?
I understand that TW merge can have some runtime effects on initial load, but sure it wouldn't be measurable compared to all the runtime JS in emotion, correct?
Also, I am looking for some articles or material on why "semantic css" is a problem that Tailwind is explicitly designed to solve.
Any points on this topic would be greatly appreciated!
Thanks!
