Mark Zuckerberg attacks 'closed' AI rivals as Meta returns to open models
TL;DR Highlight
Meta says it will resume open models, but commenters doubt its sincerity
Who Should Read
A backend developer on LLM APIs weighing whether to adopt open-weight models
Core Mechanics
- The original article was unavailable
- The FT article text was empty, so no article content is reported.
- Everything below rests only on excerpts of Zuckerberg's essay quoted in comments.
- Open-source resumption is only "some, soon"
- The quoted essay line says Meta will resume releasing some open source models soon now that Meta Superintelligence Labs is running.
- The essay calls open source a force against harmful centralization.
- Zuckerberg warns against concentrated AI power
- A quoted passage calls the idea that safety requires extreme concentration of power inherently problematic.
- Commenters say the essay runs about 6,500 words.
Community Reactions
- Opinion: LLMs are commoditizing, hurting closed models
- One commenter argued that if LLMs are commoditized, value sits in compute and coordination layers, not the models.
- That would leave closed models with a narrow business path.
- Doubt that this is really a "return"
- A commenter noted Meta's Hugging Face collections have shown near-monthly releases for a long time.
- They questioned whether "returns to open models" is accurate.
- Opinion: open weights are still hard to use
- One commenter said all frontier models are closed.
- They noted that running open-weight models like Kimi 3 yourself requires significant capital.
- Mixed views on Meta's open-source record
- Some commenters credited Meta for PyTorch, Llama, and Segment Anything.
- Others distrusted its motives and called its stance two-faced.
How to Apply
- List open-weight replacement candidates
- Spend 30 minutes today listing the features that use closed APIs.
- Mark which could be swapped to open-weight models.
- Put an abstraction layer on model calls
- Move model names and endpoints into config.
- Make provider swaps possible without code changes.
- Calculate self-hosting cost yourself
- Compare GPU hosting cost for a candidate model against your API bill.
- Use your traffic numbers, since commenters stress the capital needs.
Try It
# Paste into Claude or ChatGPT (simplified idea-level version; the original article was unavailable)
You are an LLM infrastructure consultant. Below is how our service uses LLMs.
{{current models, monthly call volume, main features}}
Questions:
1. Tabulate the risks (quality, ops cost, licensing) of moving each feature from a closed API to an open-weight model.
2. Propose an abstraction layer so switching providers needs minimal code changes.
Next: pick the easiest feature to migrate and draft an A/B test plan using an open model.Terminology
Related Papers
Mercury 3: Diffusion at scale
Scaling diffusion LLM 40x gives Mercury 3: 4–8x faster than speed-tier models, similar quality
Timestral: Mistral's time-series foundation models
A 209M time-series model ranks first on three benchmarks and runs on CPU.
DeepSeek V4.1 Flash 1017 (Max)
DeepSeek V4.1 Flash 1017 Max scores 45 on the Intelligence Index at 211 tok/s and $0.30 input.
If you don't run your own LLM proxy, how do you know whats going on?
Running your own LLM proxy shows which keys, models, and cache misses drive your usage.
DeepSeek: DeepSeek v4.1 Flash 1017
DeepSeek V4.1 Flash 1017: $0.05/M input, 1M context, built for agents
DeepSeek-v4.1-Flash-1017
DeepSeek V4.1 Flash minor update lifts coding and agent benchmarks while cutting run time and output length
Show HN: Llmspeed – feel how fast a local LLM runs before you buy the hardware