Too much of our lives are in a reactive state -- responding to events rather than being proactive. Thats a good survival mechanism -- but it causes anxiety by overanalyzing, rather than living in the moment. I think limits and boundaries are important -- but its too easy to let emotions carry us away. Rationality is only one facet of human behavior.
I think the concept is that you are awaiting the "request type". And getting back a "response type". The example is somewhat confusing since set_debug() returns a StorageRequest.
With tooling this would make your resulting type be a StorageResponse. The whole point is that you can have that "request type" be awaitable.
You may be thinking of "primitive", "simplistic" or "spartan". Things that are simple to use are not necessarily primitive.
It's simpler for library users, because they don't need to know which particular method finalizes a builder to obtain a future from it, and `.await` just works in more situations.
That's not quite the best example as someone else noted, you could better of write an API where converting to Future can be a shore of in places where await may work in the Future.
Say, `for await x in connection.item {}` not real syntax but something similar might be in Rust's future.
> Your tweet thread will be very unreadable if you use this tool.
Isn't that only the case if you don't work with their built in tool on the right to see what the thread will look like? I personally have no problem reading through a thread in this way, especially when the thread is crafted with the individual tweets in mind.
In the link you post it states "piqlWriter: data writtenas high-densityQR codesEncode binary data to 2D barcode (apply Forward Error Correction)Modulate light using a Digital Micromirror Device (DMD) to project the barcode on the film."
