Donny (강동윤)

Real men manage their own memory

🤦‍♂️

👀 you're improving faster than I ship. gonna have to make watching you a full-time job 🦀

JavaScript tools are getting a little too comfortable with Rust. 🦀 Frameworks ✅ React ✅ Next.js ✅ Astro Runtimes ✅ Bun ✅ Deno Package managers ✅ pnpm ✅ Yarn

Heads-up: stacking paid accounts on one machine for extra Codex usage can now get you locked out. OpenAI's new help page on card and device limits: - One device can only use so many paid accounts (Go, Plus, Pro 100/200/500) - Hit it and you see "Device limit reached" at sign-in, or get signed out later, even if the purchase went through - Signing out of another account doesn't free a slot - Business, Enterprise, Edu and Free don't count toward it This lands the same week multi-account switching shipped on mobile, so check before you buy a second sub. The sanctioned route to more usage is credits under Usage & Billing in the Codex app. help.openai.com/en/articles/…

Neuralink’s first product is called Telepathy. It enables high-speed communication with computers or humans simply by thinking. Output bandwidth will vastly exceed the fastest human speech or typing in a few years. Read that sentence again.

I’ve thrown a modified t3code and pretty much every frontier model working in tandem over multiple subaccounts on a relatively “low-hanging fruit” for rspack— a portable cache that’s worktree-aware. While this doesn’t solve the memory challenges exceptionally, it does have a significant impact on agentic development. The question came from Copilot: “If 80% of the code isn’t changing, why can’t the compiler share memory when working concurrently in worktrees?” Ultimately, that’s a large architectural change for rspack to just try, especially given the tools’ reliance in trillion-dollar companies, and our own company too. The path of least resistance would be making the cache portable; from there, the option to think about how to optimize or shift rye architecture could be somewhat explored, while providing users today with gains specifically targeting machine contention. I’ve been testing this using @grafana @gitlab @sentry codebases, which consume rspack already and are the general target market for large, complex, enterprise-style builds. If you are on the main worktree and create a new one, the rspack dev server, when you change a module, will only HMR one module. The warm vs. cold initial builds and hmr cycles were pretty substantial. If that agent decides to split work and makes a new worktree, rspack will rebase the cache off the base worktree, not the main one. I tested this up to 6 worktrees deep. One prominent challenge: loaders often use require.resolve or dirname, or import.meta to resolve an absolute path to a resource. In Vue loader and React transforms, this would cause the loader to rerun on a worktree. Like gitlab it cost 16k modules to be rebuilt. Finding a solution to rebasing absolute paths in worktrees was tricky. Also, you have to ensure things like the time it takes to replicate the cache (use reflink or cow) isn’t longer than rspack just rawdogging it.

My biggest concern is that if there is a clean sweep by Democrats of the House, Senate and Presidency in 2028, they will: 1. Make DC and Puerto Rico states to gain a strong majority in the Senate. 2. Open the borders and legalize everyone living in America illegally to cement a permanent majority. 3. Increase the size of the Supreme Court to gain an immediate majority. This would result in America becoming a permanent one-party state and the end of democracy in any meaningful sense of the word. All that is needed to ensure this doesn’t happen is 51 Republican senators in 2029. That is why you should vote for Republican senators this election. Other reasons are irrelevant compared to this one.

We're prototyping native language support in Next.js, starting with Route Handlers and Proxy in Go. This gives you more options for CPU intensive workloads on the server, alongside your React app.