4 ms·
What kind of work are you doing with async/await that is so improved? Very interested in what kind of code on the client that is.
by aplummer 4y ago
What kind of work are you doing with async/await that is so improved? Very interested in what kind of code on the client that is.
- tarentel 4y agoSame. I toyed with a bit for a networking stack but outside of that I haven't found anything super useful. I never went into production with it, the code I re-wrote was definitely cleaner but it wasn't really mind blowingly better that I felt the need to pursue it further.
- cvwright 4y agoI'm not the OP, but I'm updating my iOS app now to use async/await instead of callback hell for all of its networking code. It is much, much nicer. I also recently did some work with Vapor on the server side. Night and day difference there. The old Vapor EventLoop stuff was doable, if you squinted just right and concentrated really hard. The async/await version is as delightful as anything else I've ever used. Nearly as easy as writing Python.
- aplummer 4y agoThis is what I was expecting. I think for Vapor for example it's incredible because you are always in async land. For client code, because you are returning to the main thread quite a lot - I'm not seeing so many benefits.