erichocean
It seems no one understands how useless this theorem is in practice.
Engineers don't have to know why something worked in particular in order to use it, they just do.
Science later tries to figure that out.
Both are valuable, but the idea that science must be "first" is, at best, unsupported by the evidence.
Not once have I said "Mistral should not train models."
I have questioned doing yet another useless pretraining on a pre-existing, non-innovative model backbone.
Mistral spends their money and GPU time poorly, and the results demonstrate just that.
The most common Science™ failure mode.
> they'd be unable to justify their valuation or investments
I don't think they're justified now, certainly their results don't justify it. Mistral is mid at best.
> It's core to their whole value proposition that they are providing sovereign AI capabilities in Europe.
Except they don't, they are dependent on GPUs from nVidia and AMD—both American companies.
> that isn't owned
I don't know what definition of open weights you are using, but the "open" part is what allows you to use it without being beholden to American Trillion-dollar companies or the Chinese.
Mistral could do exactly what Cursor does, and post-train the model to meet the needs of Europeans.
That's a far more efficient (and useful!) use of GPUs than yet another pretrain on an outdated model backbone.
Wouldn't it be better to do something more like Cursor, and RL on an existing pretrained model if you're not innovating anyway?
And if not, why do they exist?
Update: The number of people advocating not innovating is wild. There is no reason why Mistral cannot innovate in ML, they explicitly choose not to. My point is that, given that choice, they should spend their GPU hours differently.
"Sovereign AI" is a joke, there is no substantive difference between a post-trained open weight model from an American or Chinese company and what Mistral is doing today, beyond spending 80% of their GPU hours reproducing a last-gen model's pretraining.
And compared to Go, the production observability is very good.
I also use Clojure and can observe my running app with a full REPL.
Eh, Lean was heavily developed based on feedback from mathematicians; it's not a side-effect but more like a "driving force."
Source: one of Lean's co-authors.
It's a bold strategy...
This is laughable, it's not even remotely true.
/sarc
My conversations compact hundreds of times. By the time it has done a dozen or so compactions, it fully understands the work I want it to do (and how). It's almost like having a fine-tuned Astra model.
10/10, would recommend.
You could code for it now directly, instead of having to wrap a driver API. (There's also a few API bits missing on Metal today, that are present on Vulkan—and the the hardware can do it.)
[0] https://www.slatestarcodexabridged.com/Meditations-On-Moloch
I think we'll see a bunch of different architectures over the next five years.
Okay, so no efficiency improvement?
Wow, we should really trust these people today.
Their current plan is to take the existing architecture and shorten the cycle times: move all new RLVR work into mid-training on a pre-existing base; apply new RLVR. Rinse and repeat.
If you did that daily, it would be roughly similar to how humans improve.
Have you seen the labs training them?
Total horse shit, but that's the essence of it.