Ease of use vs correctness in API design
Channel: timClicks
Date: 2023-10-04

Should you provide an easy to use default? Should you force users to make up their minds?

A discussion about the trade offs that you face as a library author designing an API, particularly as an open source maintainer responsible for a heavily used library.


📚 Resources:
- https://crates.io/crates/base64
- https://crates.io/crates/simple-base64

🦀 Rust resources:
- Tim's tutorial videos https://timclicks.dev
- Rust Documentation: https://doc.rust-lang.org/book/
- Rust Playground: https://play.rust-lang.org/
- Rust in Action (Tim's book!) https://mng.bz/4MlD
- How to Learn Rust (online course!) https://learning.accelerant.dev/how-to-learn-rust

👋 Connect with Tim:
- Twitter: https://twitter.com/timClicks
- GitHub: https://github.com/timClicks
- Mastodon: https://mastodon.nz/@timClicks
- DEV: https://dev.to/timclicks/
- Patreon (extra learning materials) https://www.patreon.com/timClicks


🔔 Subscribe to the channel and click the bell icon to stay updated with the latest videos and live streams from timClicks: https://www.youtube.com/timClicks?sub_confirmation=1

👍 Like this video if you found it helpful, and share it with your friends who are also interested in Rust programming.