The Case Against Frameworks
summary
Argues that frameworks hide behaviour, add bloat and security risk and erode developer knowledge. Gives a concrete failure: Spring reads entire upload before authorizing so tokens expire mid-upload, causing 403s; switching that endpoint to Vert.x lets headers be validated early and cancels invalid uploads, fixing the bug. Points to transitive risks (malicious packages, default admin ports), claims 98% of developers overlook security, and shows download bloat like 91 MB for a blank Quarkus project.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 7:32What is a framework?
- 12:55The framework jungle
- 15:26Framework lifecycle and bloat
- 21:26Free features you don't need
- 21:46Security risks of frameworks
- 28:08Loss of knowledge and abstractions
- 34:05When frameworks hold you back
- 36:28Be curious and critical
- 39:40Stay critical and choose wisely
- 40:22Q&A and closing
related talks
01h 00mFantastic Frameworks and How to Avoid Them
49mSpring, Jakarta EE, CDI and Other Pathologies
38mKeynote
41mJava Beyond Frameworks: Avoiding Lock-In with Agnostic Design
34mHow Do JavaScript Frameworks Impact The Security Of Applications?
13mTo Framework or Not to Framework? That is the Question
01h 01mGuide to Destroying Codebases the Demise of Clever Code
39mDevelopers kryptonite