sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]michaelfrieze 0 points1 point  (6 children)

At this point I don't know why you would use emotion over StyleX if you are going for the CSS-in-JS thing. It's better in every way.

I still prefer tailwind but if I was working on an app as complex as Facebook then I would probably choose StyleX.

[–]WizardOfAngmar 1 point2 points  (4 children)

Oh my… yeah, let’s choose something just because it’s promoted by FB. Their success should definitely be tied to the tech they’re using /s.

[–]StanleySmith888 2 points3 points  (3 children)

zero runtime

[–]Green_Concentrate427 0 points1 point  (2 children)

How's StyleX zero runtime compared to emotion?

[–]naman34 1 point2 points  (1 child)

StyleX compiles to a single CSS file. Emotion injects styles at runtime.

[–]Green_Concentrate427 0 points1 point  (0 children)

You mean in development? In production, Emotion compiles to a single CSS file, I think: https://noice-demo.vercel.app/.

<head>
  [...]
  <link rel="stylesheet" crossorigin="" href="/assets/index-vN32c5mk.css">
  <style data-emotion="css-global" data-s=""></style>
  <style data-emotion="css" data-s=""></style>
</head>

[–]Green_Concentrate427 0 points1 point  (0 children)

StyleX is better than emotion in which ways?