Skip to content

consumer async libraries and too many choices #112

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

Closed
nikomatsakis opened this issue Mar 31, 2021 · 5 comments
Closed

consumer async libraries and too many choices #112

nikomatsakis opened this issue Mar 31, 2021 · 5 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed status-quo-story-ideas "Status quo" user story ideas

Comments

@nikomatsakis
Copy link
Contributor

Basic summary

@nikomatsakis I'm not too sure if that story gathers my experience with Rust. I've not published a library yet, but I have consumed all the most popular ones. It seems that Alan and Barbara are "producers" (sorry, probably not a good word to describe people) of libraries.

My urge to write in this thread comes from the point of view of the "consumer". It's very likely that the library Alan and Barbara are writing has a limited scope. That in itself is a luxury, especially if they aim for one thing and one thing only. "Consumers" of libraries, on the other hand, will have a very long list of dependencies to work with: http client, http server, pub/sub routines, websockets, ORMs and database connections, caching in remote stores, etc.

In that regards, it surprised me the conversation about whether to use async or not. In the story I have in mind it's an absolute given. No one in their right mind would write a synchronous web server like it's the nineties

@eminence I'd be more than happy to write a sub-story. Maybe sub-stories could be linked to more than one (trust and http client)?. I think my story would begin with something like:

  1. Someone visits https://www.arewewebyet.org/
  2. As a result, s/he thinks Rust is great to write a REST API because async support seems to be ready in all those libraries
  3. And then similarity with story x
  4. But also something different

Originally posted by @cortopy in #95 (comment)

@nikomatsakis nikomatsakis added status-quo-story-ideas "Status quo" user story ideas good first issue Good for newcomers help wanted Extra attention is needed labels Mar 31, 2021
@nikomatsakis
Copy link
Contributor Author

cc @eminence

@nikomatsakis
Copy link
Contributor Author

I think @cortopy that I wouldn't necessarily write a substory -- if you want to continue a story, just reference the other story with a link in the beginning. "After Alan did foo, he ...".

@nikomatsakis
Copy link
Contributor Author

You can still add a FAQ about one story being followed by another.

@eminence
Copy link
Contributor

Yeah. I'd say we should start by just writing the story to see how it reads. And then later we can decide where exactly to put it (leave it as its own story, fold it into another story, add a sub-story, etc).

@nikomatsakis
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed status-quo-story-ideas "Status quo" user story ideas
Projects
None yet
Development

No branches or pull requests

2 participants