3 ms·
>Meanwhile, the term "open source" is massively popular. So it will get used. The question is how. Here's the source of the disagreement. You're justifying the
by unethical_ban 2y ago
>Meanwhile, the term "open source" is massively popular. So it will get used. The question is how.
Here's the source of the disagreement. You're justifying the use of the term "open source" by saying it's logical for Meta to want to use it for its popularity and layman (incorrect) understanding.
Other person is saying it doesn't matter how convenient it is or how much Meta wants to use it, that the term "open source" is misleading for a product where the "source" is the training data, and the final product has onerous restrictions on use.
This would be like Adobe giving Photoshop away for free, but for personal use only and not for making ads for Adobe's competitors. Sure, Adobe likes it and most users may be fine with it, but it isn't open source.
>The way open source software, today, generally means source available, not FOSS.
I don't agree with that. When a company says "open source" but it's not free, the tech community is quick to call it "source available" or "open core".
- JumpCrisscross 2y ago> You're justifying the use of the term "open source" by saying it's logical for Meta to want to use it for its popularity and layman (incorrect) understanding I'm actually not a fan of Meta's definition. I'm arguing specifically against an unrealistic definition, because for practical purposes that cedes the term to Meta. > the term "open source" is misleading for a product where the "source" is the training data, and the final product has onerous restrictions on use Agree. I think the focus should be on the use restrictions. > When a company says "open source" but it's not free, the tech community is quick to call it "source available" or "open core" This isn't consistently applied. It's why we have the free vs open vs FOSS fracture.