50ms, that's not much... that means, if there is an ESP8266 event, you stick the information into the Espruino interrupt queue. When Espruione comes to an JS idle, it will then work off of that queue. I guess that is the reason to have this interrupt queue in the first place, because some JS stuff (thread started by an JS interrupt) is not completed in that time.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
50ms, that's not much... that means, if there is an ESP8266 event, you stick the information into the Espruino interrupt queue. When Espruione comes to an JS idle, it will then work off of that queue. I guess that is the reason to have this interrupt queue in the first place, because some JS stuff (thread started by an JS interrupt) is not completed in that time.