-14
you are viewing a single comment's thread
view the rest of the comments
[-] taladar@sh.itjust.works 2 points 9 months ago

Creating an async application or sync application is an architectural decision. And since architecture is the sum of all decisions that are hard to change (I think this is from Martin Fowler) thus decision - async or sync - is hard to change and one must live with it.

For applications that is true but for libraries it often is not. You can e.g. design REST API libraries quite well with most of the code ignoring sync vs. async completely and only the part that actually performs requests in a general way has to handle the distinction which is why many of them include both versions.

[-] huntrss@feddit.de 2 points 9 months ago

Thanks for the clarification. This is especially true for libraries that can benefit from async.

this post was submitted on 23 Jan 2024
-14 points (23.1% liked)

Rust

5974 readers
99 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS