I wish they would have just stuck with tailwind which is capable of producing the same results, has great adoption, good docs and active development, without having to roll your own everything over and over again, as is common with css libs.
I imagine tailwind didn’t exist when they created this. Plus, there are many benefits to this approach vs tailwind; much easier to theme (crucial for fb), easier composition of styles in general and easier refactoring
I use autocomplete and headwind which is more or less just a VSCode plugin to sort the classes. Been very happy with that setup, albeit not “real” type safety
