Zubin Khavarian

software engineer ⌨ building cool stuff with @reactjs and @typescript ⚛️ exploring @threejs, @EffectTS_, @aisdk

[VoidZero @voidzerodev]

VoidZero is joining Cloudflare.

Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite+ remain MIT-licensed. Evan and the VoidZero team will continue leading them.

Cloudflare shares our commitment to open source. Together, we can keep investing in the tooling developers rely on every day, while bringing the Vite ecosystem and Cloudflare’s platform even closer together.

[Seb ⚛️ ThisWeekInReact.com @sebastienlorber]

👀 React Compiler in Rust - Exciting update from @rickyfm

TLDR:
- Rust compiler ➡️ 99.9% the same output as the original
- Confident ➡️ merge the PR within the next weeks
- Can be tested locally

The Oxc team is already working on an integration (draft PR)

[Andrew Chen @AndrewChenE]

🏎️The redesigned wheel system is finally working!
Instead of direct velocity control, wheels now spin and create grip. It feels physics-driven and fits the controller better.
Ecctrl 2.0 + demo coming soon. Stay tuned!

#threejs #threejsJourney #webdev #r3f #ecctrl #opensource

[David K 🎹 @DavidKPiano]

XState Store v4 is released 🚀

Simple, small state management for stores (like Zustand/Redux) + atoms (like Jotai/Recoil)

Works everywhere: vanilla, React, Vue, Svelte, Solid, and more. Event-driven, type-safe, batteries included, *really* agent-friendly.

npm i @xstate/store

Some new features:

[Claude @claudeai]

Introducing Claude Opus 4.8: it builds on Opus 4.7 with sharper judgment, more honesty about its own progress, and the ability to work independently for longer than its predecessors.

Available today at the same price.

[Andrej Karpathy @karpathy]

Personal update: I've joined Anthropic. I think the next few years at the frontier of LLMs will be especially formative. I am very excited to join the team here and get back to R&D. I remain deeply passionate about education and plan to resume my work on it in time.

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[Addy Osmani @addyosmani]

https://t.co/jKCIAEzai7

[William Candillon @wcandillon]

Introducing Project Redraw, a new grade of 2d primitives for Web & Native

[kache @yacineMTB]

At my company we stopped doing code reviews. There's no point now

[Faria Lima Elevator @FariaLimaElevat]

Eu e o Claude trabalhando o dia inteiro juntos:

[TANSTACK @tan_stack]

SECURITY ADVISORY — TanStack npm packages
A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package.
Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down.
Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys.
If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised:
• Rotate cloud, GitHub, and SSH credentials immediately
• Audit cloud audit logs for the last several hours
• Pin to a prior known-good version and reinstall from a clean lockfile
Detection — the malicious manifest contains:
"optionalDependencies": {
"@tanstack/setup": "github:tanstack/router#79ac49ee..."
}
Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root).
Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level.
Full technical breakdown, complete package and version list, and rolling status updates:
https://t.co/Zy8qG7PA9f
Credit to the security researcher for responsible disclosure.

[Vas Feofanov @heyvasos]

I'm absolutely tired of writing camera flyby parameters for a @threejs project and getting results that aren't quite what I wanted.

Exporting tracks from @Blender to GLB doesn't suit me, as it gives me less control and I'm subject to rebuilds every time I change the position of objects in the scene.

The solution? Write a simple visual track editor with export to JSON.

[Aiden Bai @aidenybai]

React Doctor v2 is here

Your agent writes bad React code, this catches it

Works with Next.js, Vite, React Native. Fix your app in minutes

npx react-doctor@latest

[VoidZero @voidzerodev]

🚀Rolldown 1.0 is here!🚀

Rust-based high-performance JavaScript bundler.

🏎️ Runs at native speed that’s 10~30x faster than Rollup

🤝 Compatible with existing Rollup & Vite plugins

⚡The underlying bunder for Vite 8

After 2 years, Rolldown is officially stable and has 20+M weekly downloads. Companies like Framer & PLAID are already using Rolldown in production.

Thank you to every contributor, user, and team that helped us get here.

[Claude @claudeai]

We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity.

This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.

[Kiet @FlyaKiet]

@superset_sh 2.0 is now in open beta!

For the past few weeks, we've been hitting physical limits on using Superset, my computer begins meltdown when running 20+ worktrees. Many of our users have 50+ (!!!)

Since we're 3 ex-CTOs, the logical next step is to rewrite the whole app to enable cloud workspaces. And today that's available to the public 🎉

[Vercel Developers @vercel_dev]

Introducing deepsec, an open source coding security harness.

• CLI-first
• Sandbox-based scaling
• Pluggable coding agents
• Designed for large-scale repos
• Use AI Gateway or your own subscription

After months of successful internal use, we put it to the test on some of the largest open source codebases.
https://t.co/sPxZ6izJVV

[Danny Limanseta @DannyLimanseta]

I have open-sourced the entire codebase for Tiny Skies.

You can see all the commits (100% commited by Cursor), right from the 1st day of the #Vibejam competition.

If you know coding, I'd love to seek your expertise to take a look at the code to see how "messy" it is.

I've always been very curious about how good/bad agentic coding is these days. So open-sourcing it will hopefully answer that question for me and whoever is curious.

Github repo here:
https://t.co/rdxzRoCQhA

[Priyank Rajai @Ipriyankrajai]

Let’s go 🚀 @superset_sh V2 is here and it’s a whole new level