Re: Possible issue?
This is the real problem nobody is addressing. There's a lot you can say about this code wise but, I simply remind people that while optimization may seem to have diminishing returns, non-optimized code has exponential returns. Thus a 1ms delay turning into 1^n can and will literally stop things.
A small code example mixed with a human preference can be found in Javascript. You see a lot (I mean A LOT) of people using "d.querySelector(id)" instead of the 10x faster "d.getElementById(id)". If a human doesn't really know better, what chance does AI have? Worse, what if the person who uses only querySelector() is the same person who wrote the AI!?!?!?
Biting the hand that feeds IT
