Threading/performance

[Iain-S]

We call our TurretController instance directly in the generator that serves video. However, that means that we wait for projectiles to be launched before we can continue serving video (or continue moving). It might be better to run the TurretController in its own thread and send instructions to it asynchronously to move and fire. We could even have a queue so that launching actions could be queued up with multiple clicks.

Extra nice

• [ ] It would be especially nice if the DC motors continued to spin for some time after the first launch so that subsequent launches take less time.

[Iain-S]

We should also profile the bot so we can see where we're spending most time. Perhaps in a unit test in place of a browser (or not).