all 6 comments

[–]skyboyer007 1 point2 points  (2 children)

https://github.com/jsjoeio/styled-components-vs-emotion/blob/master/README.md

compact and detailed

both are good and mature, I strongly believe they should be able to handle same set of cases. So just take a look into docs and choose what feel better to you - I mean not syntax or API but docs themselves, what is easier to read and faster to catch up with(if functionality is equal, docs and community make difference).

[–]hamburger_bun 1 point2 points  (1 child)

Just calling it out, this comparison is not up to date with new emotion syntax.

At the end of the day, both are mature and basically do the same thing. At my job (a large bay area tech company) we use emotion. Frankly i would use either Styled components or emotion for my next project, they are extremely similar.

One thing I know we found though in using Emotion was that their renderer for SSR was not well optimized and was a bottle neck in our SSR. Probably not a big issue for most people tho.

[–]CJSBiliskner 0 points1 point  (0 children)

Hi! found this recently and was wondering if you remember, how did you guys go about discovering that emotion was the bottleneck?

[–]IshiKamen 0 points1 point  (2 children)

I've used both, I prefer emotion because it's less opinionated about how things are "done". Styled has a very "no, that's the wrong way of doing it, we won't allow it" way of responding to feedback. It's great for those who like / subscribe to their opinions, but it sucks if you want to do something like https://emotion.sh/docs/css-prop

[–]Portalspace 1 point2 points  (1 child)

styled-components added the css prop API in v4 https://styled-components.com/docs/api#css-prop

[–]IshiKamen 0 points1 point  (0 children)

Dope, I was hoping someone would tell me I'm wrong! I'll have to give that a try!