The previous three posts covered how events flow from the SDK to the UI, how the timeline renders, and how tool cards visualize. This final post looks at SwiftWork's infrastructure — how data is stored, how state is restored, how Markdown is rendered, how code is highlighted, and how API keys are managed. These components are independent, but all essential to making the app usable. SwiftWork uses
An SSG benchmark across five React frameworks, from one thousand You're building a marketplace. Or a documentation site. A wiki, Five minutes. Ten. Twenty. Maybe an hour. Maybe a stack trace. You don't know in advance — and the public benchmarks won't tell So I built a benchmark for the gap. Five frameworks in a pnpm workspace, each rendering one dynamic /posts/[id] from a shared deterministic d