It’s not a charity if it becomes or serves as part of a standard. Sort of how semis and the various suppliers/buyers of that industry wind up agreeing on standards despite being competitors in some cases. Definitely things like the Linux kernel make sense to give back to - you’re ensuring the kernel lines up with your own corporate investments in a sense. A company unilaterally needing to fork and maintain their own Linux compatible kernel would need to sink a lot of time and money to come up with something as developed as the modern kernel. And it would become more expensive, unwieldy, and akin to technical debt over time.
It’s clearly not perfect calculus since so many defect from OSS, but there’s also clearly some business sense there.
> It’s not a charity if it becomes or serves as part of a standard.
Then it just transitions to a charity that everyone relies on. It's been embarrassingly difficult for people to admit this vis-a-vis Linux and the like, but it's obvious in a situation like programming languages. We rely on the enduring charity of it's authors, license-holders and distributors to write and distribute software.
"Giving back" is not an inherently cynical process. Meta has no obligation to publish these patches in the first place, much less work as a part of the community to solve a common issue. But they do, and it's just kinda part of their culture at this point. Yes, they do still gain from it; but so do their direct competitors. It's difficult to characterize as a purely business-motivated decision, because there are much greedier avenues to pursue if that's their MO.
It’s clearly not perfect calculus since so many defect from OSS, but there’s also clearly some business sense there.