Timeline for Why is it necessary for every new api to be async?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25, 2021 at 0:00 | history | tweeted | twitter.com/StackSoftEng/status/1430319017873584136 | ||
| Aug 18, 2019 at 2:15 | comment | added | spirc | My question has produced some really good thoughtful answers, thanks everyone. | |
| Aug 18, 2019 at 2:14 | comment | added | spirc | @greenoldman, you make a good point about backwards compatibility, thanks. | |
| Aug 17, 2019 at 11:00 | review | Close votes | |||
| Aug 22, 2019 at 3:05 | |||||
| Aug 17, 2019 at 8:35 | answer | added | Anders | timeline score: 1 | |
| Aug 17, 2019 at 6:54 | comment | added | greenoldman |
The only wrong decision is defaulting ConfigureAwait to true. But since you complaining, how would you design it better -- face a goal: your solution has to be back-compatible, it should provide asynchronous calls (because performance matters).
|
|
| Aug 17, 2019 at 4:31 | answer | added | Theraot | timeline score: 14 | |
| Aug 17, 2019 at 1:55 | answer | added | whatsisname | timeline score: 4 | |
| Aug 17, 2019 at 1:46 | history | asked | spirc | CC BY-SA 4.0 |