2 ms·
That sounds more like a legacy problem than a problem with the async/await model in the abstract. If you were designing a language from the ground up, why woul
by lolinder 2y ago
That sounds more like a legacy problem than a problem with the async/await model in the abstract.
If you were designing a language from the ground up, why would you implement a synchronous read operation? I would just assume that all code written in the language will treat async the way that Haskell programmers treat IO and make all IO operations async no matter what.
- vips7L 2y agoThere’s lot of programming models that don’t require async or it’s complexity. Not everything is a web server that needs to serve 100k requests.