Their audience is people who build stuff, techs audience is enterprise CEOs and politicians, and anyone else happy to hype up all the questionably timed releases and warnings of danger, white collar irrelevence, or promises of utopian paradise right before a funding round.
doesn't it get tiring after a while? using the same (perceived) gotcha, over and over again, for three years now?
no one is ever going to release their training data because it contains every copyrighted work in existence. everyone, even the hecking-wholesome safety-first Anthropic, is using copyrighted data without permission to train their models. there you go.
There is an easy fix already in widespread use: "open weights".
It is very much a valuable thing already, no need to taint it with wrong promise.
Though I disagree about being used if it was indeed open source: I might not do it inside my home lab today, but at least Qwen and DeepSeek would use and build on what eg. Facebook was doing with Llama, and they might be pushing the open weights model frontier forward faster.
> There is an easy fix already in widespread use: "open weights"
They're both correct given how the terms are actually used. We just have to deduce what's meant from context.
There was a moment, around when Llama was first being released, when the semantics hadn't yet set. The nutter wing of the FOSS community, to my memory, put forward a hard-line and unworkable definition of open source and seemed to reject open weights, too. So the definition got punted to the closest thing at hand, which was open weights with limited (unfortunately, not no) use restrictions. At this point, it's a personal preference that's at most polite to respect if you know your audience has one.
The point is that "open source" by now has an established and widespread definition, and a "source" hints that it is something a thing is built from that is open.
Is this really a debate we still need to be having today? Sounds like grumpiness with Open Source Initiative defining this ~25 years ago when this term was rarely used as such.
If we do not accept a well defined term and want to keep it a personal preference, we can say that about any word in a natural language.
> "open source" by now has an established and widespread definition
For code, yes. For LLMs, the most commonly-used definition is synonymous with open weight (plus, I think, lack of major use restrictions).
> If we do not accept a well defined term and want to keep it a personal preference, we can say that about any word in a natural language
Plenty of people do. It’s generally polite to entertain their preferences, but only to a limit, and certainly not as a forcing function. The practical reality is describing DeepSeek’s models as open source is today the mainstream mode.
I can dislike word "bread" being used to represent edible produce made from (wheat) flour, yeast and water and insist that be called dough-nut (it looks just like a big nut made from dough), but I would be frequently misunderstood.
This is why we standardize meaning of words, out them in a dictionary — so we can more effectively understand each other.
"Open Source" is normally reserved for OSI approved licenses but there are many non-OSI approved, source available licenses as well.
For example gemma4 is released under Apache 2.0 license – and can be called open source dataset.
On the other hand ie. deepseek, while publicly available weights model, is not released under OSI approved license, they released it under their own "Deepseek License Aggreement" – ie. in general it's free to use as normal OSI license but has some restrictions, ie. military use is explicitly forbidden.