zlacker

Thanks for sharing. I actually wonder now if your experience happens fairly often, and Keivan's experience infrequently, though they're fairly similar circumstances. Integrating OSS or OSS concepts into a program vs a library have different implications but the engineering work required is the same. WinGet on paper, as a product, meets all of the requirements desired by the community. To appreciate the toll it takes on your competition in the OSS community is just alien compared to rules around corporate competition, where in the US there is effectively no scrutiny around imitation. It's a natural place for a team at Microsoft to land. I wish in your case that you didn't have to find out third-hand, but it does seem satisfying to think a bespoke game engine had that much reach!

>>tiles+(OP)
Yeah, I think what we're talking about is surely the norm... Sending "hey we're releasing something built on your project" emails isn't in anyone's job description, after all. And there's no real upside, but the potential downside is that someone takes offense, tries to spoil your announcement, etc.

That said, in my case the summary makes it sound better than it actually was. The game they released was a one-off promo thing, which made a big splash for a few days but was effectively dead by the time I heard about it a week or two later. Then there followed a dialog with a separate team inside Microsoft, about hopefully updating it, which dragged on for a while and basically resulted in their bit getting updated but not mine, etc. etc. Altogether it was a big distraction and a pretty dreary episode.