← All Talks

Jacquard Magic: how to make atproto actually easy with Rust

A talk about spite-driven development and the process of using a language with a reputation for difficulty to make atproto development approachable. How do we encode the constraints (and freedoms) of the protocol in a way that makes sense and doesn't impose undue friction? What are good things to have in the defaults? There is not one right answer, and the answer, as well as the points of freedom to choose a different answer for yourself, matters. What can that ethos and its result allow you to do which you might not expect is possible?