vien 🌹

My new joy

fate 1.0: The first full Async React Metaframework New in 1.0: * Zero-Config Live Views via SSE * Drizzle Support * "Native" HTTP support (no tRPC) * Void Router * Vite plugin * Clientside Garbage Collection * Performance & scalability improvements fate.technology/posts/fate-1.0

I've moved new projects to bun, next+turbopack, typescript go, oxlint, oxlint-tsgolint, and biome. Everything feels soooo fast.

Today, we’re open-sourcing the draft specification for DESIGN.md, so it can be used across any tool or platform. We’re also adding new capabilities. DESIGN.md lets you easily export and import your design rules from project to project. Instead of guessing intent, agents know exactly what a color is for and can even validate their choices against WCAG accessibility rules. Watch David East break down this shared visual language in action👇. New capabilities and links in 🧵

@stitchbygoogle CLAUDE.md for behavior, DESIGN.md for visual intent, Karpathy's wiki .md for accumulated knowledge. we're converging on a spec-file layer that agents read before doing anything. the interesting question is what happens when these files contradict each other.

@JoshYusifov New leads? Are you looking for hiring?

What I need? > Vietnamese Salt coffee > High speed internet > New Leads

Claude users right now:

Turned my blog articles into one big design engineering skill that you can use with coding agents like Claude Code or Codex. It covers animations, component design, principles from my open source projects like Sonner, and more. emilkowal.ski/skill

We migrated @v0’s codebase from ESLint + Prettier to Oxlint + Oxfmt by @oxcproject, CI is now 3x faster. Love the OSS ecosystem.

Not knowing how to code giving you an advantage is absolute nonsense. The more you understand, the better your prompts, the better the feedback you give, the better product you ship. What will change is that the intricacies of syntax, compilers, module systems, the finer details of type systems, won’t matter as much to everyone. But you should absolutely understand how the pieces fit together. From syscall to pixels. Learn how data flows, because you’ll be able to secure your systems. Learn about performance, because you’ll be able to push your agent further. Learn about APIs, because they determine how to integrate systems. Learn about how systems fail, because you’ll be able to make reliable programs.

@shuding @nextjs What tools do you use to write this note release?

Shipped to the latest @nextjs canary: ImageResponse got 2x faster on basic images, up to 20x faster on complex ones. Plus inline CSS variables and a handful of QoL improvements.

Pure and impure func

@aidenybai With just your mistakes but the community has blame nextjs so much. Damn. You should learn and check docs carefully

we had this insane P0 bug users would get randomly logged out we had a bunch of users churn... ...turns out Next.js prefetching the /logout page

CMS → API Route → Real-time React updates This has crazy potential.

Rules, commands, MCP servers, subagents, modes, hooks, skills... There's a lot of stuff! And tbh it's a little confusing. Here's what you need to know (and how we got here).

people who hate @nextjs first learn fundamentals. if you wanna go deep , rsc, isr, edge, hydration i made a dedicated repo: github.com/renderhq/raw-b… devs cry about next.js all day. hydration bug, isr loop, streaming broken, lcp slow. 99% it’s their own lack of understanding toward the web lol they don’t get what is runtime, break file-based routing, misuse rsc hooks, fail edge constraints, double-fetch waterfalls, hydration mismatches, slow lcp, suspense deadlocks or whatever this repo shows how it really works . understand fundamentals → master runtime → app router → rsc → isr → edge → hydration this may feel some what harder . but dm me we can change it fast fast the way it would really great im curious to see all opinion cus im not only the smart next js ever lol

@nuqs47ng I would like to use nuqs a second shot. But doesn’t find the pattern and solution that work seamlessly with native URLSearchParams and startTransition with

This is my happy place. The perfect combination of 15 years of experience in: Audio engineering 🤝 Web dev 🤝 URL state This audio course is going to be 🔥🔥🔥

@Doctorthe113 @nuqs47ng But for me, most use case still using native built in with new URLSearchParams, with these and startTransition, I still need a reason to use nuqs. When using with nuqs, same re-render and lost default behavior with 2 times click e.g: pagination

I used .@nuqs47ng for the first time. Holy crap it's easier to use than I thought. Literally just replace useState with useQueryState 😭

If you've ever seen someone tweet some cool shader and thought "I don't really even know what a shader is and at this point I'm too afraid to ask" - I've written something just for you. makingsoftware.com/chapters/shade…

Open-source maps application built with @shadcn GitHub: github.com/ln-dev7/square… © @base_ui x @huge_icons x mapcn ( @sainianmol16 )

💡 Did you know? @nodejs has a built-in utility called `loadEnvFile`. It does the same thing as dotenv, with zero dependencies. The runtime equivalent of the --env-file CLI option. Here's how you can replicate the @nextjs env loading sequence with it: