Heading out from #CSSDay with a new take on mixins, inspired by @kizu's talk and experiments. Have to write up my thoughts, but in brief: How do you un-mix something, once it's been mixed in?
@kizu Yeah, I think that's generally true. But I'm curious if there are places where it helps for a mixin use to 'cascade' with itself. If applied on two overlapping selectors with different arguments, is it sometimes useful for one mixin call to 'win' entirely rather than each resulting property being compared individually.
@matuzo@sarajw yeah, not something that happens at home. but holy hell I need it after failing to sleep on the flight over. Monday and Tuesday were a single day for me.
I never check a bag. Last minute, I decided to check my bag. I'm already starting to panic. Where's my clothes? Will I ever see them again? Will I be wearing a single outfit for two weeks straight? #cssday
The man she's with is watching Mission Impossible and keeps saying "oh no. oh no. oh no."
I'm also watching MI, and pausing regularly to get a photo of whatever antics men are up to [in brackets]. Not pretending like I'm the normal one here.
I don't understand why CSS is so verbose sometimes. Why couldn't I just do: color: --brand-red;
???
Why do I need to surround every use of it with var(...)? Wasn't the double-dash prefix was specifically chosen to not clash with any existing or future properties?
It's always so frustrating writing CSS. Especially compared to all the structure, abstractions, and terseness that programming languages offer.
@keithjgrant@css@peterreeves And it's not only an implementation concern. We also tend to prioritize readability over terse writing, for the sake of authors.
We can create tooling to write the code faster as experts - but if it's hard to understand/maintain the code later, that's a much bigger issue.
Ok, most of these images still need alt text and captions. I can't do all 500+ at once. But at least I have a system (and a way for people to help out)! Thanks #eleventy