There has been another one this week. I will not pretend to have read every line of the announcement, but the shape is familiar: a tool a lot of us quietly depend on now belongs to a larger company, the blog post is full of words like "exciting" and "journey", and the comment threads have already split into "this is fine" and "time to migrate". The acquisitions have not stopped since Microsoft took GitHub last year and Red Hat folded into IBM. It is the weather now, not an event.
What I have learned to do is separate the feeling from the decision. The feeling is real. You build muscle memory around a tool, you learn its sharp edges, maybe you have even sent the maintainers a patch or two, and watching it absorbed into a corporate roadmap is a small grief. But the feeling is a terrible basis for an infrastructure decision, and most of the panicked migration threads are people acting on the feeling.
So the questions I actually ask are dull and practical. Is the format open, or am I locked into something only this vendor can read? Can I export everything I have, today, without asking permission? Is there a credible alternative I could move to in a weekend if the licence terms turned hostile in a year? If the answers are yes, then the acquisition is somebody else's problem and I can carry on. The ownership of the company matters far less than the portability of my data.
Where it bites is the tools that quietly assumed you would never leave. The ones with the proprietary export, the config that only their cloud understands, the integration that needs their account to function. Those are the ones where an acquisition genuinely changes your risk, because now a stranger holds the leash. I have a short list of tools in that category and I review it whenever one of them changes hands, which lately is often.
The honest summary is that I am not going to rip anything out this week. The tool still works tomorrow the same as it did yesterday. But I have made a note to check the export path again, and to spend an idle afternoon confirming the migration story is as easy as I think it is. That is the tax of building on someone else's product: you keep an escape route maintained even when you have no intention of using it. The week an acquisition is announced is exactly the week to dust it off and make sure the door still opens.