While witnessing powerful acts of communication during this (durational) moment - poems, speeches, live media appearances, essays, graphics, posters, songs, translations - you can see all the more clearly why governments like ours want to restrict creative subjects.
@jacobrask @_alanbsmith You're right, it's just that at the moment consumers are locked into installing and using CSS-in-JS because of our styling solution. I'd like to change that, but also still offer it as an option. But this is contrary to what Alan is saying in the first place.
@_alanbsmith The main reason being not wanting to force the overhead of using emotion on teams that don't want to use CSS-in-JS or are looking to make use of RSC.
@_alanbsmith This thread is really interesting to hear, we're actually looking to decouple our emotion/sx/styled styling solution from our components in order to enable different teams to use their CSS flavour of choice (sass,modules,in-JS etc.)
@olivtassinari@MUI_hq@JoshWComeau I suppose this pushes the building of the stylesheet onto the consumer, rather than providing one for them to consume.
@olivtassinari@MUI_hq@JoshWComeau OK, sounds good. Tbh I'm still having a bit of a problem with the mind shift of having a DS which offers a Box component for general purpose styling and how to emulate that with libs like Pigment & Panda which generate static CSS 😅🤔 interested to see how Pigment is used in MUI