He has Meta SWEs making $250k+/year labeling data in AAI. He has exactly one move and it's this: https://i.imgflip.com/atotpp.jpg
I’m not sure the incentives are really aligned when you’re pouring that much cash and liquid RSUs at someone on normal vesting schedules. News stories of some of the acquisitions state that there are engineers in Meta’s AI organisation clearing 8 figures of compensation. If you didn’t think the strategy was successful, it’s rational (if not very principled) to continue to make excuses as to why until the gravy train stops and then use that to fund your retirement and the things you’d want to do instead.
You probably don’t know how smaller models are trained then. Most of them are knowledge distilled or trained using data generated from larger models. If larger models are stopped there is no magical way smaller models will keep getting better.
So it's "release to developers" rather than "new AI model". They cannot ship the API.
I would assume you would just provide an OpenAI compatible endpoint or two? But maybe they are not doing it that way.
Who knows what they are doing though. Maybe Meta has some kind of global API mesh thing and they can't quite make it work with vLLM or Sglang or something. Maybe they are building out a whole metered cloud IaaS for AI from scratch and that's just how long it takes. Maybe it's not technical complexity and just one of the managers is a problem.
Maybe they are delaying the API release until another more competitive model finishes training and testing.
Too bad for Meta, and very sad day Llama.
Talking with OpenCode and Fireworks, appreciate any recommendations that have SOC-2 and the like