Update on current and future goals

Author: adriangb

README.md

@@ -109,25 +109,17 @@ Xpresso takes these ideas and refines them by:
 - Support for [customizing parameter and form serialization].
 - Better performance by implementing [dependency resolution in Rust], [executing dependencies concurrently] and [controlling threading of sync dependencies on a per-dependency basis].
 
-## Current state
+### Inspiration **to** FastAPI
 
-This project is under active development.
-It should not be considered "stable" or ready to be used in production.
-It is however ready for experimentation and learning!
+When I originally concieved Xpresso I wasn't sure what the goal was. I didn't necessarily want to replace FastAPI, I know how much work open source is and was not and am not willing to commit to something like that. So I always thought of the project more as a testing ground for interesting ideas for ASGI web frameworks in general and FastAPI in particular.
 
-### What is implemented and mostly stable?
+I am happy to report that in this sense it has been a _smash hit_. In the time since writing the above differences:
+- Starlette added support for middleware on routers.
+- The ASGI spec, Starlette and FastAPI added support for returning data from lifespans, which I think may be an even better idea than dependency scopes.
+- FastAPI added support for PEP593 annotations, taking direct inspiration from Xpresso's approach.
+- I've established a strong working relationship with Sebastián, FastAPI's author, and I foresee more ideas from Xpresso leaking into FastAPI in some way or another.
 
-1. Extraction and OpenAPI documentation of parameters (query, headers, etc.) and request bodies (including multipart requests).
-1. Parameter serialization.
-1. Routing, including applications, routers and routes.
-1. Dependency injection and testing utilities (dependency overrides).
-
-Most of this APIs will be _generally_ stable going forward, although some minor aspects like argument names will probably change at some point.
-
-### What is not implemented or unstable?
-
-1. Low-level API for binders (stuff in `xpresso.binders`): this is public, but should be considered experimental and is likely to change. The high level APIs (`FromPath[str]` and `Annotated[str, PathParam(...)]`) are likely to be stable.
-1. Security dependencies and OpenAPI integration. This part used to exist, but needed some work. It is planned for the future, but we need to think about the scope of these features and the API.
+So where does that leave Xpresso? It's going to stay around, but it's less likely to become a stable production ready framework: it can provide more value to the community as an exprimental proving ground for ideas than as yet another "production ready" web framework.
 
 [Starlette]: https://github.com/encode/starlette
 [Pydantic]: https://github.com/samuelcolvin/pydantic/