> It's like someone decided "async is cool!" and no one told them that interrupting the user is bad. A ton of application are doing that now. I think it has be

> It's like someone decided "async is cool!" and no one told them that interrupting the user is bad. A ton of application are doing that now. I think it has become the prevalent paradigm in many places, as a bad application of optimistic event handling. I imagine the devs thinking "It will surely load fast enough so it's not an issue", or "we can't block user interaction until everything's loaded, when the files they need might stay displayed at the same place the whole time" etc. It's particularly bad with task managers loading task lists asynchronously, when some of the first items might only be loaded last, and the list continuously moves top and down while it's loading.