4 ms·
And saved millions of developer minds not having to deal with mind bending async/await. Thanks, I prefer to wait.
by krzyk 4y ago
And saved millions of developer minds not having to deal with mind bending async/await.
Thanks, I prefer to wait.
- pharmakom 4y agoDo-notation is much simpler than callback hell
- Nullabillity 4y agoYou could have had the Loom experience 20 years ago by just spawning OS threads. Of course, there's a reason that this was discouraged... threads quickly turn into a nightmare to manage safely, especially when they need to interact.
- za3faran 4y agoGenuine question, how is managing cross interacting virtual threads any different or easier than managing interacting threads? I say this and I am greatly looking forward to using Loom in production. It's definitely the correct way to go as opposed to async/await.
- Nullabillity 4y agoIt's not. That's the problem with the thread API that Loom is so dead set on preserving, and the big improvement that promises/async/await provide over threads.
- za3faran 4y agoHow does async/await improve on managing mutable state across threads of execution (tasks/promises/etc?)
- krzyk 4y agoStructured concurrency.
- krzyk 4y agoIssue with os threads is that their number is limited. Not the issue with communication. Futures are good enough for that, if you need more then structured concurrency.