Full-stack development is dead, long live full-stack development!
summary
Compares three Java-first stacks and shows working demos: Thymeleaf + htmx renders server templates with fragment updates and infinite scrolling (no full JS app), Vaadin (Flow) builds server-driven UI components and a paged grid with built-in state and single-jar deployment, and Hilla with generated TypeScript exposes RPC-style endpoints that produce client models and client-side validation. Claims Java devs can avoid full JS ecosystems by picking based on needs: pages/SEO, traditional business UIs, or full SPA with type-safe client/server contracts.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:10My timeline
- 0:42History
- 0:57Architecture
- 1:38Application Server
- 3:00Frameworks
- 3:29Application Development
- 7:10Web Frameworks
- 11:47Rest controls
- 13:23Framework differences
- 26:46Demo with Modding
- 37:08Which framework to use
related talks
41mFull-Stack development is dead, long live Full-Stack development!
46mFull-stack Development is Dead, Long Live Full-stack Development!
28mEfficient Full-Stack Development with Java
42mReturn of the Full-Stack Developer
27m"Full-stack from the back: Building for the web with Java"
44mFull-stack web apps, 100% Java
49mThree Different Methods to Build Web UIs in Java
51mAll in on Java: Web Development with EclipseStore & Vaadin