[meta] Covering the full range of status-quo stories

[eminence]

We want to make sure that we have stories that cover the full range experiences. This list is not yet exhaustive, but is a good start from @estebank and @nikomatsakis :

Topic	Issues	PRs	Stories
Developing libraries for use in many different environments	#95 #54 #49		Barbara Anguishes Over HTTP
Targeting embedded systems or those with very narrow requirements		#85 #92	Barbara carefully dismisses embedded Future
Maintaining systems into production	#76 #75 #69	#99	Grace deploys her service and hits obstacles Barbara trims a stacktrace
Configuring and tuning systems for high performance	#87	#129	Alan iteratively regresses performance
Combining parallel processing of data with I/O	#107
Missing cool features from other languages that maybe Rust should have (JS, C#, Clojure, Kotlin, whatever)	#107
Ergonomics of using async Rust	#105 #82	#104, #99 #129	Barbara trims a stacktrace Alan hates writing a Stream Alan finds dropping database handles is hard
Learning async Rust when you already know Rust	#94, #104		Barbara makes their first foray into async Barbara plays with async
Learning async Rust when you don't already know Rust	#95		Alan started trusting the Rust compiler, but then... async Niklaus Wants to Share Knowledge
Onboarding new employees into a system built using async Rust		#104
Integrating with other async runtimes, esp. in other languages	#67
Supporting systems that integrate multiple reactors	#87
Migrating an existing sync crate to async
Supporting both sync and async apis in the same crate
Writing a custom async executor	#128	#115	Barbara builds an async executor

(We will expand this issue body with xrefs to other issues, PRs, and stories)