Why the hate against a little verbose namespace? It helps understand the context of the rule. Do you have any killer-argument or is it your opinion?
How do you make sure you separate your concerns, which is the fundamental basic of decoupling and modularization, which is essential for a bit bigger code bases
How do you make your styles re-usable, especially in the case of jsxstyle?
How do you guarantee a consistent styling without manual intervention?
For what kind of project do you recommend which CSS-in-JS style?
What is CSS-in-JS's advantage over the following examples:
I find myself still doing simple inline styles in React often. I think I take a performance hit, but while I'm opinionated on practically everything else, I haven't been able to form strong opinions on this topic. Inline seems more readable for simple things that aren't handled by a Material Design library or equivalent alternative.
Matthew Ferrin While I certainly still have my opinion about CSS-in-JS, I really recommend not doing inline-styles. There is a reason why they were banned from the HTML5 spec entirely.
Also, there is Vanilla CSS, which means you do your styling without any library or framework at all. Whenever you need to do simple things, don't use a library and try to workaround it when it doesn't fit 😉
Marco Alka
Thank you for your write-up. Just some questions:
.login button[type="submit"] { background: blue; }