Design decisions, refactoring, and framework internals
FuryStack now ships a real cross-node event bus and a Redis Streams adapter, so identity invalidation and entity sync finally work across pods instead of just within one lonely process.
The latest FuryStack update throws @Injectable in the bin, replaces classes with tokens, and finally clears the runway for the next big TypeScript upgrade. Here's what changed and why your @Injected properties are about to get really lonely.
How FuryStack turns Yarn deferred versioning into changelog entries without guessing, vibes, or heroic memory.
Polling is dead, long live push. FuryStack's entity sync system gives you real-time, server-pushed updates over WebSocket — with delta replay, reference counting, auto-reconnect, and a state machine that actually makes sense.
FuryStack's @furystack/cache isn't your grandmother's memoization wrapper — it's a full state machine with observable entries, stale/cache timers, capacity eviction, and a UI component that renders it all for you.
Shades v12 replaces the rendering engine with a VNode-based reconciler and drops lifecycle callbacks in favor of hooks — here's the full story.
Using extension methods was fun at the beginning but I've ran into more and more problems with them