so this "var ai=" thing or using window.ai or setting this value, may have a problem with upcoming changes on the chrome browser and possibly also nodejs as it usually mimics browser apis precisely, as it hides window.ai maybe it should be renamed to prevent future potential conflicts to another name.
this is just speculation. but I think maybe google will want window.ai for itself.
so this code may break when interacting with other code in the future perhaps.
specially if done globally.
https://github.com/justintaddei/tictactoe/blob/5409de2e6d4328bbea37fa223a0046bee863a473/main.js#L3
so this "var ai=" thing or using window.ai or setting this value, may have a problem with upcoming changes on the chrome browser and possibly also nodejs as it usually mimics browser apis precisely, as it hides window.ai maybe it should be renamed to prevent future potential conflicts to another name.
this is just speculation. but I think maybe google will want window.ai for itself. so this code may break when interacting with other code in the future perhaps. specially if done globally.
see this link for details. https://developer.chrome.com/docs/ai/built-in
right now it's behind a flag but in the future this may change.
not clear on the timeline tho.
have an awesome day!