Ah, that‘s the angle you’re coming from.

In this regard you are right. I could’ve chosen AGPL and use it in my commercial project nonetheless. I wasn’t aware of that at the time, and that was a mistake.

That said, I don’t expect all users to notify me. But if a company like Apple, with millions of users, exposes me to even a fraction of its users - then yes. I expect a mail beforehand. I did not sign up for this.

But I agree with your last part again ;)

To be honest, I wasn’t aware of this option when I wrote this library. Nowadays I would chose this path.

I did not want to make a business out of this library. I don’t want money for it.

All I would’ve wanted is that the people at Apple would’ve given me a heads up beforehand, so I would’ve been prepared for it and not caught on surprise. And a that they do a version upgrade when I release a new bugfix release.

This is not a license issue. I was well aware of the consequences when I chose the MIT license. This is not about money.

Yeah, well. What should I say. I wanted to use it in a commercial project, too :)

Yeah, I was surprised, too. I guess they implemented stuff using Ruby and didn’t bother to write an in-house implementation. 🤷‍♂️

Apple deployed a library I wrote to every mac on the world, and additionally bundles it with Xcode.

Apple users reported some bugs, that‘s how I found out.

I never heard a word from them. No patches, no bug reports, nothing, they didn’t even bother to refresh the bundled version.

I think in the meantime they removed it from macOS but still bundle it with Xcode.

I mean, I didn’t any money, but some appreciation would’ve been nice, and a version refresh…

If you are curious: it is this library: https://github.com/ckruse/CFPropertyList

Edit: appreciation as in: a mail with a notice that they did so.

💯 came here to say that.