Anthropic's landmark S-1 filing showcases unprecedented enterprise AI growth—reaching $16.3B in H1 2026 revenue—while pioneering a novel public benefit corporate governance model.
sec.gov/Archives/edgar/data/…
Ray Wu retweeted
We've decided to sunset Arc on December 22, 2026.
That's not an easy sentence to write. We spent years building Arc and celebrating each and every release along the way: we have so much pride and love for what we made alongside the Arc community.
Our priority is to deliver best-in-class security for our members. Keeping a browser secure takes constant, dedicated work that is only increasing in the age of AI. Dia was built from the ground up to meet today’s security standards, so that's where our engineering and security teams will focus moving forward.
We've worked to make switching to @diabrowser as easy as possible for Arc members. Here's how:
· Your passwords, bookmarks, extensions and history come over to Dia seamlessly.
· Spaces, Folders, and Tab Groups are in Dia and import over with your data intact.
· Dia now surpasses Arc benchmarks in stability, speed, and security.
· The browser features you use in Arc are free in Dia, and the AI is optional.
Thank you for using Arc, for pushing us to make it better, and for building alongside us. The team that made Arc is the same team behind Dia, and some of our most ambitious work is just ahead. We'd love for you to be there with us when it lands.
"Programmers, he says, became a priesthood that everyone else had to go through to get anything out of a computer, and AI has ended that monopoly much as the Reformation ended the clergy’s." thoughteconomics.com/david-h…
Ray Wu retweeted
everyone's sharing motion graphic videos that Opus 5.5 made, and it's genuinely insane
everyone says they created it with "one prompt", but my one prompt video looked mid
so i went through a bunch of these videos to see how they were actually made, and found the workflow that works
here's how to generate pro level motion graphic videos w/ opus:
1. get reference videos to direct from -> whatships.com
pick 1-2 videos whose style you want and tell opus to match them. naming a style works way better than describing one
without a reference, opus falls back to its default look: centered text, gradient background, everything fading in
that's why so many of these videos look the same. a reference gives it the pacing, the type and the transitions to copy
2. install @HyperFrames_ or @Remotion so opus can build the video
both let opus write every scene as code and render it straight to mp4. no video editor
without one, opus can only describe a video or hand you a rough html page you have to screen record
with it, every frame is exact, and when you ask for a change it edits one line and re-renders instead of starting over
3. install @21st_dev for high quality components in the video
real buttons, cards and UI components made by design engineers, instead of whatever opus invents on the spot
without it, opus draws your product UI from scratch and it looks off. wrong spacing, placeholder boxes, fake-looking buttons
anyone who's used good software can feel it in a second, and the whole video reads as cheap
4. steps 1-3 were context + setup. now dump all of it into opus
your brand (logo, colors, fonts), screenshots of your real product, the reference video, and a quick braindump of how you see the video
then ask for 3 storyboard variants
without this, opus guesses your colors, your font and what your product even does. the video could be for any startup
with it, it could only be yours. and 3 variants means you pick a direction instead of fixing the first idea it had
5. pick the storyboard you like
ask for one still frame per scene before anything moves. fixing a storyboard is way cheaper than fixing a render
without this step, you only find out scene 4 is wrong after the whole thing is animated, and every fix means re-rendering. a still frame takes seconds to change
6. let claude cook
then give notes like a director: "slow every zoom to 0.7x", "hard cut here", "push in on the button"
without notes, the first render is usually 80% there, and that last 20% is what makes it look pro. vague notes like "make it better" get random changes. camera words get exactly the change you want
everyone has the same model. the context you give it is what makes it look pro
let it cooookk
Ray Wu retweeted
sharing some notes on typesafe 🤝 coding agents:
docs.google.com/document/d/1…
we likely will never have time (ever again) to play ourselves, but hope the that the community goes WILD (and makes me look like a naive idiot)
Ray Wu retweeted
A couple of trends I'm seeing across the industry.
Which ones are you observing, that I missed?
This is me
I ended up leaving OpenAI, not because there's anything wrong with OAI (I actually think they're underrated as a biz), but because to me, building commercial software doesn't feel fun anymore
Because agents write ~all the code:
- There’s less human to human collaboration, so it’s a lonelier experience
- You’re constantly context switching and not going as deep into the code, which means there’s ~zero flow state
- Most of the job becomes code review and trying to reduce complexity, which is very mentally draining
Again just my experience, and none of this specific to OAI. There are many people who seem to be enjoying building software in this era!
But I've always wanted to try making films, and now seems as good a time as any
Ray Wu retweeted
Here is my interview with Christopher Nolan: are you a bard for a civilization at dusk?
Ray Wu retweeted
For 50 years, software engineering ran on code rationing. Writing code was expensive, so we rationed it carefully through roadmaps, RFCs, prioritization meetings, and scope reviews.
This created a role: the No Engineer. No, that won't scale. No, we don't have bandwidth. No, that's out of scope. No, we need a design doc first. The No Engineer was valuable for 50 years. Every "no" saved real money. Their judgment was the rationing system.
LLMs will be the end of code rationing. Code is cheap now. And while the No Engineer is explaining why something can't be done, the Yes Engineer has already shipped three versions of it.
If you're a Yes Engineer, the next decade is yours.
An Interview with Michael Morton About E-Commerce in the Age of AI stratechery.com/2026/an-inte… via @stratechery
ClawSweeper 0.2.0 🦞
The OpenClaw maintenance bot now handles the loop:
issue → @clawsweeper fix/build → guarded PR → review → repair → re-review → automerge
Still conservative. Much less manual.
clawsweeper.bot
Ray Wu retweeted
Did a very different format with @reinerpope – a blackboard lecture where he walks through how frontier LLMs are trained and served.
It's shocking how much you can deduce about what the labs are doing from a handful of equations, public API prices, and some chalk.
It’s a bit technical, but I encourage you to hang in there - it’s really worth it.
There are less than a handful of people who understand the full stack of AI, from chip design to model architecture, as well as Reiner. It was a real delight to learn from him.
Recommend watching this one on YouTube so you can see the chalkboard.
0:00:00 – How batch size affects token cost and speed
0:31:59 – How MoE models are laid out across GPU racks
0:47:02 – How pipeline parallelism spreads model layers across racks
1:03:27 – Why Ilya said, “As we now know, pipelining is not wise.”
1:18:49 – Because of RL, models may be 100x over-trained beyond Chinchilla-optimal
1:32:52 – Deducing long context memory costs from API pricing
2:03:52 – Convergent evolution between neural nets and cryptography
An Interview with F1 Driver and Venture Capitalist Nico Rosberg About the Drive to Win stratechery.com/2026/an-inte… via @stratechery




























