A post titled Google's Antigravity Bait and Switch is leading Hacker News today and generating significant discussion across the developer and tech community. The story is touching a nerve because it speaks to a pattern that engineers and businesses who depend on Google products have experienced repeatedly over the years.

The term bait and switch in this context refers to Google's history of launching products with significant fanfare, building user and developer ecosystems around them, and then deprecating or shutting them down in ways that leave those ecosystems stranded. Google Reader, Google Plus, Stadia, Inbox by Gmail, and dozens of other products have followed this arc. Developers and businesses build on Google infrastructure because the scale and integration are unmatched, and then absorb the cost when Google pivots away.

Antigravity in this context appears to reference one of Google's developer tools or APIs, and the complaint driving the Hacker News discussion is that the product was positioned as a long-term infrastructure investment before being effectively abandoned or significantly degraded.

The reason this story resonates so broadly is that it is not really about one product. It is about trust, and specifically about the gap between the trust required to build a business on someone else's infrastructure and the reliability that infrastructure actually delivers. For independent developers and small companies, that gap can be existential.

Google is not unique in this behavior among large technology companies, but its scale makes the consequences of each shutdown larger. Today's Hacker News top story is a community processing that frustration in real time, and the volume of engagement suggests the conversation is far from over.