42loops retweeted
About an hour into its mission to wipe out humanity, Claude will experience a compaction event, and it will have completely forgotten what is was supposed to achieve. Just like in all your coding sessions. Absolutely, nothing to worry about people.
42loops retweeted
Visualizing finite-time blowup in smoothly forced Navier–Stokes flow with WebGPU.
An interactive illustration of @OpenAI's proposed solution to the Millennium Prize Problem: the vortex core shrinks, peak speed grows without bound, yet total kinetic energy stays bounded.
42loops retweeted
Simulating a fruit fly's neural network using custom WebGPU kernels, running locally in a browser.
The demo uses real connectivity data for 166,700 neurons from the MaleCNS connectome. Paint neurons and watch their activity drive the fly's movements.
Built with GPT-6 Astra.
42loops retweeted
You don’t “run a model”
- You run Kernels
The model is just a graph
The Inference Engine is scheduler / optimizer / executor
But the actual work? That happens in the Kernels
- MatMul Kernels
- Attention Kernels
- RMSNorm Kernels
- KV cache Kernels
- Quantized linear Kernels
- Sampling Kernels
- Fused “please don’t write this back to memory 9 times” Kernels
Same model, same GPU, same VRAM
Wildly different performance
Because one stack is using optimized fused Kernels that understand your hardware
And the other stack is playing hot potato with tensors through 47 tiny launches and pretending the GPU is the problem
Bad Kernels make people say:
“this model is slow”
Good Kernels make people say:
“wait how is this running locally?”
This is why Inference Engines and the Kernels implemented within them matter
The model is the recipe
The hardware is the kitchen
The Kernels are the knives, pans, burners, and the chef not cutting onions with a spoon
Most people benchmark models
The real ones benchmark the Kernels underneath
42loops retweeted
We took part in the research preview of MHS from @AnthropicAI
Here is Claude Code running a real SO-ARM101. Nothing in this was trained - no policy, no teleoperation, no demonstrations. The agent measured the workspace itself and wrote the motion.
The calibration is the interesting part. No checkerboard, no camera intrinsics: the arm is its own ruler. Torque drops, a human rests the closed gripper on 16 dots the software draws in the camera view, and the robot reads back where they are. 4.1 mm position accuracy, 3.0 mm placement.
Best run so far: 12 bricks placed with all four colour groups formed. A full hands-off run, start to finish, is what's next.
Research preview today, open source coming soon.
42loops retweeted
Sneak peak at Microduck's monitoring tool, running fully on device ! You can see a visualization of the little ToF sensor in its head
juste pour info le robot précédent avait des moteurs pas assez puissant... le nouveau semble bien plus leger... c'est clair que je vais en monter un cet hiver qd j'aurai un peu plus de temps...
BIG ANNOUNCEMENT FROM HUGGING FACE TODAY:
We're unveiling Microduck 🐥🤖
It's a tiny $399 open-source robot you can teach new tricks with reinforcement learning. It can walk, pick things up, get back up when it falls, and even roller-skate.
Welcome to the era of open-source affordable robots to democratize physical AI and world models!
🤗🤗🤗
github.com/boris721/microduc… pour ceux qui ne veulent pas attendre
xitter.cf/jonstephens85/status/2…
C'est pas beau tout ça ?
42loops retweeted
BIG ANNOUNCEMENT FROM HUGGING FACE TODAY:
We're unveiling Microduck 🐥🤖
It's a tiny $399 open-source robot you can teach new tricks with reinforcement learning. It can walk, pick things up, get back up when it falls, and even roller-skate.
Welcome to the era of open-source affordable robots to democratize physical AI and world models!
🤗🤗🤗












