When we "keep specificity flat" in #CSS we have to give up on semantic selectors and built-in naming conventions, in return for⦠also giving up control in the cascade.
We can't avoid the cascade, it applies to all styles. We can only refuse to use the tools that are available for *managing* the cascade.
Start using Cascade Layers, and let your specificity run wild. It's a useful tool!
I am very tired of conference talks that start by telling me
- everyone is excited
- these tools are the future
- now is the time to get on board
- you don't want to be left behind
You do not need to be excited for the machine they wish could replace you already
People now trust 'information' coming from black box algorithms controlled by just a few companies, as though they have "looked it up" somewhere,
but also we can copy/paste relevant code snippets, with some amount of success! so it's great, actually! β¨
this industry is fucking stressful
What are your favorite little day-to-day use cases for the #css :has() selector? Anyone using it in their reset yet?
Q: How is AI being used in web development?
A: CEO's stole our copyrighted work, and are now using it to threaten our jobs, lay people off, and cut our pay.
I'm not holding up well.
I wanted to be more clear in my #btconf talk, that when i talk about the cascade, i mean a resistance to fascism. I mean that politics live inside our tools.
but i took out the slides where i say it out loud. And Im sad about that. But also knew I wouldn't make it through the talk. I couldn't say "I'm illegal in two states already, and worse is coming"
In case you thought i was just talking about the web. I'm sorry I couldn't say it more clearly.
