The use of inline styles and !important in #Javascript #Frameworks who are presented by people dissing the Cascade and specificity seem to not understand that inline styles are powerful because of their *specificity*. !important works for about 10 of us in our user style sheets.

The @w3c is doing a fine service in specs to reiterrate their audience is implementors. This was not clear to many in early years. This by design makes any tech interpreted by a browser BROWSER TECH first. To understand #Webdev is to understand browsers/user agent implementation.

We now live mostly in a browser monoculture. Around 1998 <layer> v <div> dramas in DHTML (hahaha) and I thought "maybe an open source shared engine would bring better interop, backward compatibility, #A11Y, competitive features anywhere but the rendering engines." Oh, naive me!

Then, #HTML5 via @WHATWG - I loved many ideas but it was clear it was mostly for application development, not information rich Web sites. And which software had to change the most? User agents. This goes back to my issues with Cartesian Duality - we need most of what we created.

We have so much knowledge. So many tools. And yet, who says: "ARIA here isn't needed, the HTML is sufficiently semantic." "This site has full keyboard access." "A radio button and a checkbox should not behave the same way." "Can I disable all but the content?" "IS there content?"

Despite enjoying color and esthetics as a study and for environment, I came to appreciate real #WebDesign when @mezzoblue pub'd CSS Garden. Working on the book Zen of CSS with him pushed me a bit to make peace with -prefixes for progressive #CSS, interop and backward compat.

NONE of that including prefixed #CSS (aka browser ignores if not capable of parsing) got in the way of what is my primary assistive device to meet #social and #a11y needs. I'm not hating on JS or Frameworks. I do want to see true #CSS as browsers work where able. !important

Snark goes so far. I want to help. Conditions: I want poking and peer review input. Goal: CSS current specification explained in specific, easy, meaningful bits no longer than a paragraph of detail with an example. Master user agents, master the tools. Strategize wider. SCALE UP!

And, I would be most excited to have JS-First and JS Framework contributors/devs to talk with a bit more about our tools, inclusion, things we can each do to help each other. There used to be the backend/frontend dev hate. Now we have front, back, full. We all learn, we grow.