You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2
Original file line number
Diff line number
Diff line change
@@ -87,8 +87,10 @@ Please checkout our [goals](#goals) before drawing your own conclusions.
87
87
- more suited for highly dynamic and interactive applications
88
88
11.**Atomic**: ability to generate atomic css classes and increasing reusability, reducing style duplication
89
89
- this generates a separate CSS class for each CSS property
90
+
- it's a bit more difficult to debug/inspect when dealing with many class names applied
90
91
- you'll get larger HTML files, because each element will contain a large number of CSS classes applied
91
92
- theoretically [atomic CSS-in-JS](https://sebastienlorber.com/atomic-css-in-js) reduces the scaling factor of your styles, [Facebook is doing it](https://www.youtube.com/watch?v=9JZHodNR184) as well
93
+
- it's debatable if the styles size reduction, is greater than the html size increase (what is the final delta)
92
94
12.**`className`**: the API returns a string which you have to add to your component/element
93
95
- similar how you would normally style React components, so it's easy to adopt because you don't have to learn a new approach
94
96
- you'll probably have to use string concatenation, or interpolation, to combine styles
0 commit comments