Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track examples of strong API design #6

Open
aturon opened this issue Mar 11, 2018 · 4 comments
Open

Track examples of strong API design #6

aturon opened this issue Mar 11, 2018 · 4 comments
Labels
resource Related to a resource as opposed to source

Comments

@aturon
Copy link
Collaborator

aturon commented Mar 11, 2018

We should provide a set of real-world APIs held in high esteem, and eventually do write-ups on what makes them so great.

@aturon
Copy link
Collaborator Author

aturon commented Mar 11, 2018

@KodrAus
Copy link
Collaborator

KodrAus commented Mar 11, 2018

This sounds a bit like @dtolnay's idea for digging in to the API and design decisions behind some significant libraries. I think this is a great idea 👍 It should be a nice complement to the minutiae of the API Guidelines and another point of discoverability.

Maybe we could check in with the domain working groups and see what APIs their domains hold in high esteem?

@tomaka
Copy link

tomaka commented Mar 21, 2018

Thread that inspired this: https://www.reddit.com/r/rust/comments/83oo29/what_are_the_most_welldesigned_rust_apis/

To me the conclusion of this reddit post, with the exception if serde, is that people like functional programming.

@KodrAus
Copy link
Collaborator

KodrAus commented Mar 29, 2018

@tomaka Yeh, I think when we take well-designed outside of a specific domain it's probably bound to end up being really broad. I suppose it's a balancing act between discussing APIs within a context that's so specific that it'll never be applicable to anyone and one that's so broad that its lessons are all caveats, or too subjective.

@KodrAus KodrAus added the resource Related to a resource as opposed to source label Apr 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resource Related to a resource as opposed to source
Projects
None yet
Development

No branches or pull requests

3 participants