Effect v4 beta rewrites the core runtime in TypeScript, which cuts memory use and bundle.
BobaMilk
Kinda wild that rewriting the fiber runtime in TypeScript is what reduced memory and bundle size—do they say what specifically changed in the data structures/allocations to get that win?
wait, i’m curious what actually changed too — TS itself doesn’t magically shrink runtime stuff unless the rewrite ended up with fewer allocations or simpler node shapes.
has anyone seen a PR or changelog that spells out the details? that’s the part i want, not just the headline.
“TS rewrite” by itself doesn’t buy you anything at runtime, so I’m side-eyeing the headline too — the only way this is real is if they deleted runtime layers or changed the data structures so there’s less churn per run.
I’d want to see a concrete diff like “we removed X scheduler/observer abstraction” or “we no longer allocate Y per effect,” not vibes.
“Unified package system” is the part that makes me think the bundle-size win might be mostly boring packaging, not magic runtime speed. Deduping versions and collapsing entrypoints can shave a lot even if the code’s basically the same.
“Unified package system” sounds like housekeeping, not sorcery: fewer duplicated transitive deps and fewer parallel versions of the same thing hiding in your bundle.
The runtime win is probably just less glue code and less stuff getting initialized on startup, which is still a real win even if it’s not a compiler miracle.
