-
AmeliasBrain Not one in particular - general research into 1) the origins of CSS 2) the details of the cascade 3) various CSS conventions/paradigms (several of them directly inspired by imperative paradigms) 4) learning JS, & starting to see where these ideas come fromPermalink On twitter.com
❤️ 4 Favorites Mood +2 🙂
-
AmeliasBrain They really do provide useful concepts in CSS, to an extent. What frustrates me is that the porting of those ideas tends to bring along concepts that *don't* fit CSS – like the assumption that side-effects, context, and state changes are bad.Permalink On twitter.com
-
AmeliasBrain I don't have a complete answer – but it's something I'm constantly working on, & would love to see more community awareness of the issue: A recognition that CSS is fundamentally different in important ways, & we can't port other paradigms directly.Permalink On twitter.com
-
AmeliasBrain I think a CSS paradigm has to embrace: - silent failure & progressive enhancement - everything is contextual - the cascade is fundamentally a guide for CSS architecturePermalink On twitter.com
-
AmeliasBrain For example: "specificity" isn't some abstract set of rules that are there to trip us up. It actually describes an organizational concept. More specific selections override less specific selections. That is also true in visual design tools.On twitter.com
-
AmeliasBrain My new convention will be called Cascading Cascading Style Sheets. CCSS. 😆Permalink On twitter.com