- on my way to reworking the ops stack I use, and @dhh’s new OS is on my list of things to try.
a few observations for the coming years:
- computers won’t exist in their current form. reworking linux and adding a new look and feel on top might not be enough.
- the computational constraints of fully agentic workloads are quite unique.
- humans will need to be less and less involved, and most of the “inputs” we provide can be brief.
- we will see complete rewrites of browsers, operating systems, and even the hardware layers behind modern computers.
it’s going to be wild.
some more thoughts here: https://t.co/lMaA4IDbve.
Here's my conversation with @DHH. He is back for round 2! It was an epic fun 5 hour conversation about the future of programming, AI, Linux, and human civilization.
It's here on X in full and is up everywhere else (see comment).
Timestamps:
0:00 - Episode highlight
1:27 - Introduction
2:56 - Programming with AI agents
18:14 - How software will change
27:30 - AI impact on open source
37:21 - Building Omarchy Linux distro
47:05 - Vibe coding vs agentic engineering
1:00:06 - The end of manual programming
1:10:24 - Advice for programmers
1:22:30 - Surviving Internet Hate
1:31:46 - Programming setup for AI Agents
1:44:11 - Obsessing about speed
2:07:06 - Voice prompting vs typing
2:21:05 - Best AI coding models
2:37:55 - Best AI coding harnesses
2:50:57 - AI video generation and filmmaking
3:10:28 - Fatherhood
3:38:35 - Linux will win the desktop
3:49:51 - PewDiePie
3:59:24 - Future of programming
4:22:17 - Politics and immigration
4:53:54 - Longevity, over-optimization, and fear of death
5:05:38 - Eternal recurrence and future of human civization
data vendor lock-in is done. a service didn't expose an API to retrieve my data, so i got an agent in the browser mode to "click" on 300 downloads instead over a few hours. de-regisreted from the platform.
🎙️This week, @AnnaRRose chats with @sergey_nog from @circle about @arc and its TEE-based Privacy Sector. They discuss why they chose TEEs, the tradeoffs between hardware trust and composability, his recent debate w @secparam and more!
https://t.co/2H9WnsToq0
@veorq@fabgenovese amongst the crypto-native community, that's true. but the institutions care about a combination of trust and security. TEEs have been used by many in various products. various TEE products actually have certifications to act as HSMs.
After 24 hours and lots of love from the zk community I’m even more convinced that this is the last privacy project in the blockchain space 🤣. No boys and girls, there is no admin key. Read the paper and use AI to do some fact checking or ask it to come up with at least something a little bit more interesting than that.
Since we started the project, I’ve been telling the @circle team that this will be the last privacy solution in blockchain space.
And we delivered.
What we have built is not just privacy-preserving smart contracts. Instead, it's a paradigm shift in how blockchains, composability, and privacy need to co-exist. The design addresses the two core failures of prior privacy systems: lack of composability and a painful developer journey.
Pure cryptographic privacy is elegant, but expensive and hard to scale in practice. Instead, this design builds on the now-established trend of cryptographic enclave technologies.
What we’ve built is a parallel execution environment on @arc :
Arc public blockchain continues processing cleartext blocks, while the Arc privacy sector operates as a parallel privacy-preserving virtual machine that processes encrypted transactions.
State, transactions, and user accounts remain hidden. Validators cannot inspect what’s inside, even if they try to snoop or are compromised. Yet they continue producing blocks for both public and private states in sync, committing to each state tree.
That is also a major difference from designs that rely on access control, which inevitably creates failure points and data exposure risk.
The public and private state composition is the game changer for developing. For the first time, users can move between private and public state within the same block space. No bridge. No extra wallet layer. No separate accounts. A single transaction can move between private and public execution with zero friction.
Furthermore, the environment gives users post-quantum protection by design. Transactions and accounts remain encrypted, and public keys stay protected under post-quantum secure algorithms. Any account or asset created inside the privacy sector is automatically post-quantum secure.
The result: a fully composable privacy sector on @arc that is post-quantum secure and seamlessly interoperable with public execution.
This is the last privacy layer in Web3.
See the whitepaper: https://t.co/Fz0IMafS2a
@circle@arc
@davidtperk@IanSNorden i'm saying validators have no visibility beyond seeing a an encrypted byte-string while building a block. there is no leakage. it's the minimal one can do over any encrypted tech.