3 ms·

I used to think this way. In reality, you're not separating concerns, you're separating technologies (CSS and HTML). Should your backend authentication code li

I used to think this way. In reality, you're not separating concerns, you're separating technologies (CSS and HTML). Should your backend authentication code live in the same file as your billing logic? Probably not. Separate concerns. But when the concern is "a sign up component's look and feel", I see nothing wrong (anymore!) with lumping it together. In fact, I prefer it. Just my two cents.

jf- 8y ago
Logic, layout and style are inherently separate parts of a component. Separate concerns in other words. Ideally they should have separate definitions. This is the cleanest and most maintainable structure. The cycle seems to be to separate things clearly, then mix them back again, then separate them out again. I’ll happily skip the mixing part of this cycle. However, that said I don’t want to give the impression that I’m being proscriptive here, other developers are perfectly free to have their own preferences just as I have mine.