Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

agreed. the examples don’t show the real pain. it is when every method returns Future or Promise. and you have to map each result. and many languages don’t have good support for that so you end up with lots of nesting. writing synchronous function signatures is much simpler to maintain.

there’s 2 language level syntax features i see that make this better:

one is scalas for comprehension. this lets you write async code that reads like imperative synchronous lines. the other is async/await, which let’s you write synchronous code that behaves like async



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: