i kind of wish there was a way with @scope in CSS to say “inside this selector, turn off all other CSS rules except my base styles that i’ve tagged somehow that should stay on” https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/At-rules/@scope

haven’t thought through this, just thinking out loud about what might help me

(basically disabling the cascade i guess except for a few specific things)

maybe this exists already in CSS?

ok i think this is an example of how to do exactly the thing I want from the CSS spec https://drafts.csswg.org/css-cascade-6/#example-463550a5 (assuming that all my components that I want to be independent are labeled with data-scope=)

@b0rk Seeing modern CSS, I have such mixed feelings. It looks so much better than what I learned in 2003, but also "in my day, we didn't need all this fancy stuff, we just suffered and cried and used tables!" which is a ridiculous reaction but it's there in my lizard brain.

I look forward to "Hell Yes! CSS! (2!)"

@rjbs I remember being quite empowered when the float hacks started getting popular. Then when everyone did 960 px grids…

Now with that, flex, grids, dialogs, I'm getting strong C++ programming vibes: Sure, there's a reason for ever single feature in all of that, but… points at specification thiccness.

@b0rk

@mhd @rjbs i don't know anything about C++ but CSS feels manageable to me for some reason.

I think it's because like yeah grid is hard but I only ever have to deal with my own code, so even if it takes me like 7 years to get comfortable with grid that's ok, grid is really useful so I'm happy to make the investment. I don't personally feel any pressure to learn new CSS features unless they solve a specific problem that I'm struggling with.