Early days or not, Google fucking deleted my IDE and wiped my settings. It took them days to roll out a fix, by which point I had migrated off Antigravity.
Watch out for VRAM/RAM. When programs on WSL tired to take more than there was available it was crashing my WSL hard and even corrupting files on the virtual drive attached to WSL in a very strange manner that made recent files just disappear. I had at leat two projects that had to be rebuilt from past conversation with AI because all their files were gone after few crashes.
I asked codex to write WSL config to prevent crashes. It put some limits on WSL and the situation stabilized, but I lost all trust for WSL anyways.
Genuine question: what are the good parts of Windows that keep you there? I've been such a happy gamer/coder/media editor on Linux for so long that I really don't understand how Microsoft isn't dead yet.
My Linux laptop and desktop both handle gaming and waking from sleep just fine. I'd be more surprised if they didn't. You might like CachyOS or Bazzite if you try it.
The only thing I remember about CORS is that it takes way longer than expected to debug, by design the error messages sent to the browser are intentionally gutted, and CORS error scenarios are hard to tell from other failure modes atfirst glance.
> by design the error messages sent to the browser are intentionally gutted
A CORS error is not "an error message sent to the browser", it is an error generated by the browser, because the browser has decided it cannot permit the request. (Though certainly a server can not understand a CORS request as such, and returned a weird response, which would then end up getting translated to a CORS failure.)
I think what the person you're replying to is trying to say is that the web-accessible error message (i.e., the one that JavaScript running in the sending page can read) is intentionally opaque and somewhat misleading, because a more helpful error message would leak information about the response that the sending origin isn't supposed to have. There's typically a more helpful error message in the dev tools (which JavaScript running in a page can't access), but you have to know where to find it.
The message in the dev tools is, at least for Chrome, extremely developer unfriendly: The blocked request is displayed in a very strange way, without any information that it was blocked, nor that CORS was the reason for it, nor how that decision was made based on the preflight request.
You have to already know from experience that these strange devoid-of-information requests have been blocked by CORS, then find the preflight request, and there you will find a bit more information, but still much less than would be possible to show.
Showing more information would, AFAIK, not circumvent the layer of security that CORS (or actually origin isolation, which CORS makes an exemption from) adds. My best guess is that this just had very low priority when building the dev tools.
They nuked anti-gravity and installed their codex knockoff in place. The vs code fork IDE and all your settings with it have been removed. Reinstalling the anti-gravity IDE, as it's been renamed does not bring back any of your settings or extensions.
reply