it's very interesting how many replies i've gotten about maintainability and clean code being still important. i would argue that that is no longer true and we all need to update our priors on what Good Code really means in 2026. clean code has always come at a cost - performance. indirection and making code readable/understandable for a human is not free, it often comes at the cost of worse performance. we have historically been okay with this because of Moore's Law and the fact that most code is not on the hot path. these principles also came from a time where humans maintained code. it made sense to optimize for humans then, but it makes less sense now when agents are already writing all the code. we will in fact probably discover and come up with new principles: principles of agent friendly architecture (i plan to write more thoughts about this soon)

Best part of AI is shattering dev's egos, the worst part of this industry. You are not special. Your code actually sucked like everybody else's. You were never the smartest person. The things my sales guy BIL and designer brother are doing is beyond anything I have done.

Strongly agree here that when we get this right we will unlock some truly incredible patterns and performance wins. Streaming async signals from first paint to pre hydration to post hydration is a huge unlock.

Thanks for asking! I have an internal bench and @octanejs is already ahead on js-framework. Yet @trueadm and I think it's far its ceiling: instead of using the universal renderer, we should compile specifically for Lynx. Codex on it. Stay tuned!

life update: after 4 incredible years at Vercel leading the Next.js and React teams, I’m joining OpenAI to work on Codex as an IC. ChatGPT and Codex have completely changed how I build. Getting the chance to help shape where this goes next was too exciting to pass up. I learned an absurd amount at Vercel, and I’m excited to bring some of it with me. onwards :)

When a human writes it, there's a rawness, and emotion to the tone. There's slight bias, there's accent, there's a unique word tone that the person writing has that makes you think "Ah, that's Dominic, or that's Ryan".

Much love to the Solid team and congrats on launching Solid 2! Cursor has largely completed this migration from Solid to React. We also have since converted all our scss and Tailwind to @stylexjs, in both Cursor and in @bot. The new agents window is 99% React, with a few stragglers left that we have yet to migrate. The big motivation for this migration was for perf and maintainability reasons. We have seen that in practice, it is actually quite easy to create perf footguns for yourself in signal based approaches when reactivity causes a large amount of accidental fan out in large and complex apps. It probably was a skill issue. But in the age of agents, choosing what pitfalls you're okay with is an important decision. I think it's fair to say that every UI framework has its pitfalls and that no perfect one exists yet. For us, React was the most known quantity, and we found that solving its problems is actually quite straightforward and boring: exactly what you want when you're trying to ship! Something interesting I also observed is the uncanny valley effect of non-React frameworks looking like React. I think it confuses agents, because in my experience, agents were quite bad at writing good Solid code. Everything ended up being accidentally tracked which caused so many perf problems. React Compiler solves most of your perf problems with over-rendering. The remaining cases just take some manual memoization or refactoring/composition, which an agent can easily do. The nice thing about useEffect is that it's like an unsafe {} block in Rust: it shows me at a glance where the problems are. @bot (which is 100% React) is built on Dune, our in-house, agent friendly React framework for desktop apps, which actually bans useEffect outright and only exposes it indirectly through framework-provided hooks. Highly recommend setting something like that up for yourself!