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

In .net, mandatory async/await for new API is also making things that were easy harder. Async introduces multithreading where there wasn’t, breaks call stacks (debugging harder), deadlocks in certain conditions but not others (asp or winform vs console), forces you to handle what happens if the user interacts with the UI before your function is done executing, etc.


This is definitely true. Just trying to download a file can become an async chain hell-hole.. it's asyncs all the way down!


The pain in the chain is mainly in the main().


> forces you to handle what happens if the user interacts with the UI before your function is done executing

Thank goodness for that. No more of UI suddenly freezing completely and stops accepting input just because internet connection is flaky. Async or other slow operations should not be running on the UI thread.




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

Search: