Notices by Esteban K�ber :rust: (ekuber@hachyderm.io)

To err is human, but to royally fuck up, you need automation.

I don't have the answer. For things like #accessibility, I do think an attitude that it falls under the spirit if not the text of the American ADA coupled with government grants to get experts to work on the problem would help. I can't fault a solution not appearing fully formed, but don't need to be happy with the results either.

#OpenSource and #FreeSoftware is predicated on people "scratching their own itch", with the expectation that if a solution is useful to you, it will likely be useful to others. But that breaks down when it comes to hard, niche problems that require specialized knowledge and skills. Things like good accessibility in desktop environments doesn't happen without lots of effort, knowledge and intent.

@jwz non-cyclists that are confused by activism think that activists are attracted to cycling, when the reality is that becoming a cyclist very quickly radicalizes one into becoming an activist. Nothing crystallizes strong opinions as being frequently threatened with death by at best indifferent and at worst aggressive and antagonistic people.

Are you (or know) a blind programmer? What is your set-up? TTS or Braille? What OS do you use? IDE/editor? What limitations, annoyances or show-stopper issues have you encountered? Particularly interested if you use Rust, but happy to hear about the state of developer experience for blind programmers more generally.

#Rust #RustLang #Programming #accessibility

My coworkers ask for help with a #Rust compiler error... *once*...

...and then I run and try to mechanize my explanation and put it back in the compiler.

Our dev tools need to talk to humans in the way humans talk. Nobody is an expert on everything, helping newcomers (with better tools, better docs, better errors) helps *everyone*.

That's really the trick behind the rustc diagnostic output: it's not about a technology, its an attitude.

#RustLang #programming

rustc doesn't have good diagnostic messages because of some technological breakthrough. It has good diagnostic because we look at how people use our tools, noticing when things confuse people, and changing the output to match people's mental model.

"#Rust development is going too fast (because they are stabilizing features I don't care about) and going too slow (because they are not stabilizing features I care about!"

There are only so many #RustLang contributors, hours in a day, days in a year to get to everything *now*, and some features are reliant on *other*, less flashy work that needs to happen before they can be even attempted.

But people are putting in a lot of work, the codebase changes so quickly that it is hard to keep up.

@cliffle virtuous feedbacks beget vituous feedbacks. People expect more, so they simultaneously demand and give more. I hope that it continues spreading to more and more places.

"You can say 'all are welcome,' but if wolves and sheep are both welcome then you're only going to get wolves. The the smart sheep will go somewhere else and the naive sheep will be eaten and processed. [...] Refusing to choose is a choice. It's a choice in favor of the people who prey on others and who refuse to acknowledge the humanity of those they hate."

We run a well oiled machine.

Step 1, @eliza complains: https://twitter.com/mycoliza/status/1592248742060920832

Step 2, we fix it: https://github.com/rust-lang/rust/pull/104469

Step 3, it lands on nightly: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=043ea14f2d5e54113fc40b5b175d18ed

From now on, obligations introduced by trait bounds will check whether the type is longer than 50 chars, and if it is, dump it into a file so that the CLI output doesn't become an unreadable mess.

#rust #rustlang