BUGFIX: now testing a fix for an epic race car edition bug that may be present throughout the code but now I finally know what to look for.

It was a stupid simple common mistake but as so many say, JavaScript race conditions can be very challenging to find.

But still it's no excuse for how gut wrenchingly long this has taken me to find.

But in my defense, they only seem to occur randomly every other day or so on these long trips and previously the MacBook Air was simply too slow to do my serious development with. I resisted because I did not want to spend the thousands it would cost to get something "serious" but once the MacBook Air aged out I pondered another MacBook Air but even the new ones are underpowered. So I picked up a new Mac Mini which could be gotten with larger amounts of RAM which freed me up to get a more useful developers laptop ... The System 76 which has 40 gigs of RAM and a 4tb SSD. Stupid fast running Linux. It's a godsend.

So all told it cost me over $3500 to find this bug. I should just have done it ages ago.

But, of course, I didn't know.