this post was submitted on 22 Jun 2024
691 points (98.6% liked)

Programmer Humor

23310 readers
1013 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
691
Corpos being corpos (sh.itjust.works)
submitted 11 months ago by alphacyberranger@sh.itjust.works to c/programmer_humor@programming.dev
37 comments fedilink hide all child comments
 
top 37 comments
sorted by: hot top controversial new old
[–] cjk@discuss.tchncs.de 126 points 11 months ago* (last edited 11 months ago) (3 children)

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.

[–] SomethingBurger@jlai.lu 106 points 11 months ago (1 children)

MIT License

Hopefully, you learned your lesson.

[–] cjk@discuss.tchncs.de 37 points 10 months ago (2 children)

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

[–] thevoidzero@lemmy.world 34 points 10 months ago (1 children)

You can use your library for commercial projects that you have. Just have dual license that requires payment for commercial use or something similar. You don't have to pay yourself

[–] cjk@discuss.tchncs.de 12 points 10 months ago (1 children)

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

[–] thevoidzero@lemmy.world 3 points 10 months ago

I think that's why Github suggests MIT as default. Unaware people will just put that. Most open source people just code things they want without thinking much on other aspects. We really need some sort of enforcement to stop companies banking on voluntary work done for the community.

[–] JPAKx4@lemmy.blahaj.zone 12 points 10 months ago (1 children)

I mean isn't it your library? You can make any exceptions you want lol

[–] GreyEyedGhost@lemmy.ca 12 points 10 months ago (3 children)

Here's the core issue. The developer didn't know his rights, and made a mistake. I'm not criticizing, people make a career dealing with crap like this. But if you want to make a business out of something, it's worth it to do some research or talk to a lawyer. I believe the MIT license has its place but, from what the OP said, this isn't it.

[–] cjk@discuss.tchncs.de 7 points 10 months ago (1 children)

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.

[–] GreyEyedGhost@lemmy.ca 6 points 10 months ago (1 children)

You specifically said you chose the MIT license because you wanted to use it in commercial projects. That's business, no matter how small. As the owner of the property, you could have used any and all licenses available to you. Also, if you wanted to require users of your code to attribute or notify you, you could have. If you want to be disappointed in their behavior that's perfectly fine, too. Corporations usually disappoint if you have any altruistic expectations of them.

[–] cjk@discuss.tchncs.de 13 points 10 months ago (1 children)

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 ;)

[–] Tikiporch@lemmy.world 7 points 10 months ago

You're a good person.

[–] Wilzax@lemmy.world 3 points 10 months ago* (last edited 10 months ago)

Agreed. Free licenses should NEVER be applied to Apple-specific tools. They don't want to help the FOSS community, so we shouldn't help them back. Make them pay for it, or make them make their own version.

[–] acockworkorange@mander.xyz 1 points 10 months ago (1 children)

the MIT license has its place

Garbage, that’s its pace.

[–] GreyEyedGhost@lemmy.ca 1 points 10 months ago (1 children)

A cogent argument. I'm convinced!

[–] acockworkorange@mander.xyz 1 points 10 months ago

Praised be the copyleft!

[–] mattd@programming.dev 46 points 11 months ago (1 children)

Really funny/interesting that they use an external library to handle a format that they created!

[–] cjk@discuss.tchncs.de 13 points 10 months ago

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

[–] Nighed@sffa.community 7 points 11 months ago

It's probably a single dev that made the decision, then moves onto something else. They (probably?) don't have the ability to just raise a recurring PO etc to easily pay you and don't care enough to worth through the paperwork.

If you had a paid licencing model they may have done it, or just found another lib/ wrote their own.

[–] milicent_bystandr@lemm.ee 103 points 11 months ago (1 children)

Make your MIT-licensed library big enough that the corpos use it, then switch it to AGPL just before you add a really important and tricky feature they've been waiting for.

[–] Z3k3@lemmy.world 53 points 11 months ago (1 children)

The rich text editor my work uses in its product dud this 🤣

While they are looking to jump to something else they will get at least 1 or 2vyears worth of fees out of them

[–] alexdeathway@programming.dev 30 points 11 months ago (1 children)

Ckeditor lol?

[–] Z3k3@lemmy.world 16 points 11 months ago* (last edited 11 months ago)

Bingo

[–] madcaesar@lemmy.world 41 points 11 months ago (3 children)

I really wish we could have a license like if your revenue is 5mil + you have to kick in something to the devs

[–] perviouslyiner@lemmy.world 40 points 11 months ago

That is essentially what the "Post-Open Source" idea is trying to do.

[–] kionite231@lemmy.ca 7 points 11 months ago (1 children)

5milkick license

[–] Alexstarfire@lemmy.world 2 points 11 months ago

Makes 10 thousand fists in the air seem like nothing.

[–] Technus@lemmy.zip 6 points 11 months ago

I wonder why I haven't seen a standard open-source license for this.

[–] victorz@lemmy.world 22 points 11 months ago (2 children)

Comapnies 🥺

[–] kambusha@sh.itjust.works 13 points 11 months ago

Comapny, bro

[–] lurch@sh.itjust.works 11 points 11 months ago

lol Comapenis

[–] pkill@programming.dev 13 points 10 months ago

AGPL RULEZ

[–] Honytawk@lemmy.zip 9 points 10 months ago (2 children)

So how difficult would it be to update the library to include a blacklist to those big corpos taking advantage of your code?

[–] magikmw@lemm.ee 14 points 10 months ago (1 children)

Easily done with licences. Corpo is scared of licensing.

[–] scrubbles@poptalk.scrubbles.tech 19 points 10 months ago (1 children)

I really like the GPL license for that reason. Take it, use it, be merry. But don't you dare use it in a closed source project, and you have to give me credit

[–] magikmw@lemm.ee 7 points 10 months ago

Credit and release any changes you made to it. No freeloading.

[–] PM_Your_Nudes_Please@lemmy.world 3 points 10 months ago

Just use a GPL license instead. It allows use with credit, but requires that usage also be released for free. Meaning that it can’t be used by corpos and their closed-source projects.