3 ms·
> Async I/O gives awesome performance, but further abstractions would make it easier and less risky to use. Designing everything around the fact that a program
by Analemma_ 7y ago
> Async I/O gives awesome performance, but further abstractions would make it easier and less risky to use. Designing everything around the fact that a program uses async I/O, including things that have nothing to do with I/O, is crazy.
Microsoft kind of tried to do this with the new APIs for UWP: pretty much everything is async, the blocking versions of APIs were all eliminated, so there was no way for the async-ness to "infect" otherwise synchronous code. It was actually a pretty nice way to program; it's a shame it never took off.
- nicoburns 7y agoThe JavaScript world is pretty close to this. Not quite everything is async, but almost everything is async-first.
- Matthias247 7y agoThe javascript world was forced into this. Since it doesn't (or at least didn't) expose threads, everything had to be non-blocking. Otherwise programs would be non-responsive all the time.
- yakz 7y agoThey're finally opening the APIs (already have, I think, to some extent) for use with normal desktop apps and "UWP" apps outside of the Store. You can even embed the new UI stuff inside of Forms and WPF apps via XAML islands. They also lowered their portion of the revenue share considerably for Store apps, afaik.