Far from the same technique, imo. But very clever all the same!
I'm not familiar with React. I tried reading a primer on it and got really bored. Couldn't imagine how it would change my work. Then again, I'm mostly a UX designer who works with code rather than an "engineer" focused…
CSS is a different technology for a different complementary purpose to, say, markup or business logic. That's why we have the separation of concerns principle. If business logic is doing CSS's work, design changes MESS…
Just to clarify, the "layout versus presentation" thing isn't just for its own sake. It's to avoid having to implement design changes in two places (the CSS and the template/backend). By using template logic and classes…
Far from the same technique, imo. But very clever all the same!
I'm not familiar with React. I tried reading a primer on it and got really bored. Couldn't imagine how it would change my work. Then again, I'm mostly a UX designer who works with code rather than an "engineer" focused…
CSS is a different technology for a different complementary purpose to, say, markup or business logic. That's why we have the separation of concerns principle. If business logic is doing CSS's work, design changes MESS…
Just to clarify, the "layout versus presentation" thing isn't just for its own sake. It's to avoid having to implement design changes in two places (the CSS and the template/backend). By using template logic and classes…