Return of the Full-Stack Developer
summary
Argues that full‑stack web work speeds feature delivery by removing front/back handoffs, using concrete examples: Vaadin, Spring Boot with JTE, Quarkus + Qute, JSF are used to implement the same product-list app in four repositories (github: SemaCH/fullstack) and the lazy‑loading grid works across implementations. Shows HTMX adding HTMX‑driven lazy‑loading and fragmentization to template engines, demonstrates paging-on-scroll via htmx attributes, and warns a real project ended up managing hundreds of HTML fragments as a real cost.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker background
- 1:27Rise and fall of full stack
- 8:11Challenges of client-server split
- 13:29Advantages of full stack development
- 19:47Front-end styles and frameworks
- 24:43Demo of Vaadin framework
- 27:37Jakarta Faces overview
- 29:47Template engines like JTE and Quarkus
- 33:40Dynamic UI with lazy loading
- 37:40HTMX for dynamic templates
- 41:09Conclusion and efficiency benefits
related talks
41mFull-Stack development is dead, long live Full-Stack development!
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
52mWhy Full-Stack Is the Future of Web Application Development
27m"Full-stack from the back: Building for the web with Java"
41mWhy Full-Stack Is the Future of Web Application Development
41mRapid server side full stack web development with ViewComponents and htmx