> In a normal situation this would have been fixed simply by adding a wait primitive to the language which would schedule the events when the result is still be

> In a normal situation this would have been fixed simply by adding a wait primitive to the language which would schedule the events when the result is still being fetched... 80 percent of the programming is about doing one motherfucking thing with another motherfucking thing and you need both of them to complete the action. I love JavaScript, but I totally agree with this.