Session overview
Two senior engineers from our team take opposing positions on which framework wins for a series of representative project types — marketing site, blog, e-commerce storefront, SaaS app, and content-heavy editorial product. Live code demos and benchmark data throughout.
The framework
The session is structured as five rounds. For each project type:
- Both engineers state their pick and one-sentence justification.
- A live code demo of how the project would be structured in each framework.
- Benchmark data: bundle size, Lighthouse scores, TTFB.
- Discussion of operational trade-offs.
- Verdict.
Key topics covered
- Astro's partial hydration model — when it shines, when it gets awkward.
- Next.js App Router and server components in 2026 — where they live up to the hype.
- The image, font, and asset stories for each framework.
- Deployment options and edge story comparisons.
- Team velocity and DX considerations.
Demo projects
The session includes live coding of:
- A marketing homepage with hero, features, and pricing — built in both frameworks side by side.
- A protected dashboard page with server-side data fetching.
- A product detail page for an e-commerce storefront.
The conclusions
The session ends with a decision rubric the audience can apply to their own projects. Spoiler: there's no single winner — the right answer depends on the workload, the team, and the deployment target. See our blog post on the decision.
Recording
Contact us to request the recording or schedule a private session with our team.