Finally back on track with book got stuck on markup and CSS as core to accessibility and how we since 2009 are failing to evolve markup since HTML5. I am not anti API. I'm not against scripting. (1)

I am distressed how easily we switched programming paradigms midstream at the expense of accessibility, inclusion, digital divide, internationalization, meaningful content. We will learn and learn again that one size, one code, one methodology, one idea simply will never fit all.

Same.

Interesting, Alex. Do you remember a conversation we had a long time ago when you were writing Frame for Chrome? All about interoperability and specs. You seemed passionate about widening application approaches. Has anything specifically brought you to a different point of view?

That was more than a decade ago, and we did (& do) need to expand the platform for interactive work. WC was part of that. But the community has gone berserk with inappropriate, underperforming tech at exactly the wrong moment. You can trace my arc here: infrequently.org/series/perf…

By 2016, the data was so dire that I was pulling the fire alarm: youtube.com/4bZvq3nodf4