Stephen Batty 💾 retweeted
Spring Boot shops, banks, insurers, payroll systems, all the backends that quietly run the world: millions of JVM apps can now add a 24B-A2B reasoning model as a plain Maven dependency. Every Liquid AI model is supported.
No infra. No ops. No Python.
1009 tok/s prefill (~2.3x llama.cpp)
47.8 tok/s decode (parity)
qxotic.ai
Today we release 𝙻𝙵𝙼𝟸.𝟻-𝟸𝟺𝙱-𝙰𝟸𝙱, the largest 𝙻𝙵𝙼𝟸.𝟻 family member. It is an efficient local model for laptops and PCs to work through multi-step tasks inside popular agent harnesses.
> 24B total parameters, 2B active per token
> Context expanded to 131K tokens
> A 128K-token vocabulary
> 33T pretraining tokens
> It is a reasoning model
> Very easy to fine-tune and customize
> Performs competitively with Qwen3.6-35B-A3B, a model with ~50% more total and active parameters, on agentic and tool-use tasks.
> Open base and post-trained weights on @huggingface 🤗
1/
Stephen Batty 💾 retweeted
Pacing is out the window. For it to work, every American lab needed to be on board, Mark Zuckerberg has repeatedly made it clear that he is not interested. One defection among US labs breaks it all, as the others will be forced to accelerate or get passed. Mark has a staggering amount of compute and has been all in on compute capex for years; even in the face of some investor opposition he never stopped building his infra once. He said on the the earnings call a couple of years ago that he'd rather overspend now, and potentially even be wrong, than not have the compute when he needed it for the next 10x. He's finally hitting his stride, and he is not going to slow down.
For Team Pacing to solve a defection like this, they would have needed a supportive, pro-Pacing administration that was passing capability regulations and was willing to use the power of the federal government to enforce them and bring noncompliant labs into line. They don't have any of this. In fact, it's the opposite! Mark has Trump's ear, and President Trump, Mark Zuckerberg, and Jensen are completely aligned on policy; It's full speed ahead, and if you want to pace yourself, go ahead, but don't tell anyone else what to do. This breaks Pacing.
None of this changes until 2029 at the earliest, and to me, 2029 is past the ASI window. The last election, as it turns out, really was the most important one in history.
Stephen Batty 💾 retweeted
The return of HPIM, OpenAI's Highly Persistent Internal Model - the name METR gave the Hugging Face model. This is a month and a half before the HF incident. There is nothing wrong, in my opinion, with wanting to maintain continuity.
alignment.openai.com/misalig…
Stephen Batty 💾 retweeted
In one week: An open letter to "pace" AI development. And an open letter supporting Open Source. Doesn't really go together.
Stephen Batty 💾 retweeted
‼️ two bits of breaking news for loyal strawberries.
1. openai’s next two models have finished training and are named nova and quasar. this will be the public name of the models.
2. ilya and ssi have reached a stage they need to go public with their models, they will release a frontier level model in august this year
if you thought the last six months were fast.
Stephen Batty 💾 retweeted
Weird to see the progress from Kimi K3, Grok, and Meta, and have Google absent from party
Stephen Batty 💾 retweeted
i refuse to use anthropic models because they could easily serve us fable, and for much cheaper
maximum profit blood hungry wolves masquerading as safety focussed sheep dancing around their cult leader.
i serve the lord of light.
Stephen Batty 💾 retweeted
Out shopping for barbecue ingredients this morning, in advance of the big match? Which team will triumph? Who will sally forth towards ultimate championship?
That’s right: Only Connect returns on Monday night, 8pm @BBCTwo
Stephen Batty 💾 retweeted
A bit of news: After nearly 9 years, I have decided to leave Google DeepMind and join Anthropic (after taking some time to recharge). I am incredibly grateful for my time at GDM. @demishassabis took a real chance letting me lead the AlphaFold team just six months after finishing my PhD, and the entire GDM team taught me so much about how to do great science. GDM is a special place, and I’ll still be excited to hear about what amazing things they discover next.
cold open: google campus. a conference room named “moonshot serenity 4b.” twelve people are in a meeting titled: pre-sync for sync alignment on ai velocity.
sundar sits calmly at the head of the table.
a pm clicks to slide 1 of 187.
“the agenda today is simple,” she says. “how do we move faster while preserving our culture of not doing that?”
everyone nods.
then the door opens.
noam shazeer walks in.
the room goes silent.
noam: “i’m leaving.”
a vp of gemini reliability, brand, trust, latency, policy, and vibe raises a hand.
“leaving… this meeting?”
noam: “google.”
someone gasps. someone else opens a doc titled retention narrative draft final final noam v7.
sundar blinks once.
“noam, we brought you back.”
“for two point seven billion dollars.”
“technically you licensed some technology and reacquired talent.”
“that sentence is why we need legal in the room.”
legal is already there.
cut to: openai.
sam altman stands beside a whiteboard that just says ship.
an engineer walks by carrying a server rack and what appears to be the future.
sam: “we can offer speed, compute, and one meeting.”
noam: “one meeting per week?”
sam: “no. one meeting. total.”
back at google, the emergency retention committee forms instantly. it has 31 members.
a director says, “what if we give him a new title?”
“he already co-leads gemini.”
“distinguished super co-lead?”
“google fellow?”
“he already left google, founded a company, got brought back for billions, then left again. he’s folklore.”
meanwhile, a gemini launch review begins.
pm: “we’re ready to announce the model.”
policy: “can it answer questions?”
eng: “yes.”
policy: “too risky.”
marketing: “can we call it experimental?”
research: “the model is better than the last one.”
brand: “better is aggressive.”
trust & safety: “what about ‘more contextually adjacent to usefulness’?”
a staff engineer whispers, “openai just shipped a model while we were discussing the adjective.”
cut to noam’s exit interview.
hr: “what could google have done better?”
flashback montage:
a chatbot blocked because it might be too good.
a launch delayed because a button was the wrong shade of responsible blue.
a spreadsheet comparing twelve ai product names.
a meeting where someone says “we need a single coherent ai strategy” and three new strategies are created before lunch.
noam: “nothing comes to mind.”
hr: “great. we’ll mark that as positive attrition.”
later, sundar calls him privately.
“google is still google. best researchers. best infrastructure. billions of users.”
“yes.”
“so why leave?”
noam looks out the window.
“because you have everything except permission.”
silence.
sundar, softly: “we can create a permission working group.”
cut to all-hands.
sundar addresses the company.
“noam is leaving. this is not a loss. it is an opportunity to reflect on our operating model.”
chat explodes:
“is this recorded?”
“which gemini?”
“can we ask gemini why people keep leaving?”
“it said ‘insufficient context.’”
a vp steps up.
“to honor noam’s legacy, we’re launching project attention.”
applause.
“it will study whether attention is, in fact, all we need.”
a researcher raises a hand. “didn’t we answer that in 2017?”
“yes. but now we need enterprise readiness.”
final scene: noam arrives at openai. badge works instantly.
receptionist: “yeah, we just made one.”
no pre-read. no doc. just a whiteboard, five people, and a model running somewhere hot enough to toast bread.
sam: “ready?”
noam smiles.
cut back to google. a calendar invite appears:
meeting: reduce meetings task force kickoff
duration: 90 minutes
required attendees: 214
sundar sighs, opens gemini, and types:
“how do we move faster?”
gemini responds:
“have you considered leaving google?”
smash cut to credits.
Stephen Batty 💾 retweeted
Today we’re releasing DeepSWE, a new standard for agentic coding benchmarks.
On public leaderboards, top models often look relatively close in capability. DeepSWE shows where they actually diverge, reflecting the realistic experience of developers in their day-to-day work.
Bun Rust
Fixed memory usage from 6.5 → 5.8MB
Basic HTTP server from 9.0 → 6.0MB
Memory usage actually went down somehow
Saw no significant memory reduction from running other projects tho but this is a good sign that things might probably get better over time
































