@ahmetcantryk
5 min read
React Compiler: Goodbye useMemo?
A codebase with 400 useMemo calls and still-broken re-renders is what pushed us to React Compiler 1.0. What it auto-memoizes, and where useMemo survives.
Tag
A codebase with 400 useMemo calls and still-broken re-renders is what pushed us to React Compiler 1.0. What it auto-memoizes, and where useMemo survives.
Field notes on caches that lied: the four caching patterns, TTL guidance by data type, and why one hot key going stale can bring your database down with it.
Bun's raw HTTP throughput beats Node.js by 4x — until a real Postgres query collapses that gap to 3%. The 2026 data on speed, cold starts, and migration risk.
Drizzle vs Prisma in 2026: Drizzle ships a ~7.4 KB bundle while Prisma 7 swaps its Rust engine for WASM. Bundle size, edge cold starts and a decision table.
PgBouncer pooling boosts performance but can silently break RLS tenant isolation in transaction mode; here's the SET LOCAL fix and CVE-2026-6664 patch.
Can you get traces without touching application code at all? We break down eBPF's kernel-level visibility, the 2026 stack, and its real limits.
Rate limiting isn't one algorithm choice — it's three decisions: where you enforce it, what key you use, and only then which algorithm to run.
A list endpoint was firing 400 queries and taking 6 seconds to load. Here's how we detected the N+1 problem and cut it down to 2 queries with eager loading.
Signals are a fine-grained reactivity model: only the changed value updates, no virtual-DOM diffing. Here's how Solid, Angular, Preact, and Svelte 5 use it.