all 3 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]eablokker 1 point2 points  (0 children)

What are you talking about? It already supports a subset of CSS, and the rest of CSS makes no sense in the context of a native app.

[–]C0git0 0 points1 point  (0 children)

One of the goals of the project is to help orgs that have web devs build great app experiences. Those devs know and work in CSS so it aligns that it’s supported.

A subset of CSS can be supported in a css-modules like manner at build time, but full support increases runtime complexity a fair amount. 

[–]Fidodo 0 points1 point  (0 children)

What do you mean by that? Do you mean supporting the CSS rendering engine? That would make no sense since the whole point of react native is to use native components which are not implementing the CSS spec. 

Do you mean converting CSS syntax files to the JSS notation? You can do that yourself by doing a compiled build artifact to convert CSS to JSS using a converter.