why sx but css

hi, friend , this project is very good

but i have a question

in new styles , why sx but css

why this?

<Box
        sx={{
            ...  ...
        }}
>

why not this?

<Box
        css={{
            ...  ...
        }}
>

if we use css, Mental burden will is very small, very easy to learnning and use

---

like className、htmlFor， in react, it’s not good design

why not htmlClass + htmlFor

or className + htmlName

thank you very much

[michaldudak]

The is no standard css prop on components. There is style instead. style -> stylex -> sx for short.

[oliviertassinari]

Once we ship v5 to a larger audience (currently at 1.7% of v4), it will be interesting to see how the community reacts to the sx prop that extends the behavior of the css prop that styled-components and emotion have made popular. For instance, one could argue that we should also expose a css prop, simply for the sake of not changing habits.

For now, it feels that @stfenjobs didn’t provide arguments to really have a discussion. Personally, since sx extends css, it seems better to not fragment the audience between two ways for doing almost the same thing.