Notices by Matt Campbell (matt@toot.cafe), page 3

On the other hand, the "handmade" GUIs I've seen are, without exception, inaccessible with screen readers. Say what you will about software built on towers of abstractions and dependencies; these things do make it more likely that applications will be accessible.

It has taken me a while to come to terms with the fact that my solution, being a library and an abstraction layer, and one written in a programming language (Rust) that tends to be polarizing, will not be acceptable to everyone. I've been aware of the Handmade community since shortly before I started AccessKit, and I now believe I've fretted too much about trying to make my library acceptable even to that group, to the point of wondering whether I should have used Rust at all.

I've tried to put forward a compromise with my AccessKit project, allowing a variety of GUI toolkits, based on different architectures and implementation tradeoffs, to share accessibility infrastructure, in the hope that many more non-bloated, or at least less-bloated, GUIs will be accessible.

@mjg59 All right, is there a way that we software developers can disable all speculative execution on our own machines so we can find out the new performance targets that we'll eventually have to meet?