AI summary by TwinMind
Is full stack even real anymore?
Theo - t3․gg
31m 36s
Full Stack Framework Proliferation Problem
- New full stack frameworks appearing weekly: Laravel, Rails, Next.js, TanStack Start, SolidStart
- Frameworks differ fundamentally in purpose and control level
- "Batteries included" term inadequate to describe differences
- Confusion stems from multiple interpretations of "full stack"
Code Review Tool Sponsorship (CodeRabbit)
- AI-powered code review tool at $12/month basic, $24/month pro
- Automatically reviews PRs, leaves inline comments in VS Code
- Claims 90%+ accuracy after initial training period
- Prevented dozens of production bugs according to user
- GitHub VS Code extension integration highlighted
Framework Categorization Framework
- Full Stack Definition: Backend + frontend integration
- Makes backend/frontend work together easier
- Should run on both sides
- Fuller Stack Definition: Backend + frontend + database + auth + middleware + API generation + extensive tooling
- "Batteries included" approach
- Comprehensive application framework vs simple full stack
Python Framework Comparison (Flask vs Django)
- Flask: Minimal approach
- Simple import, route definition, HTML return
- Similar to Express.js philosophy
- Django: Batteries included
- Extensive setup documentation (Apache, Postgres, MariaDB)
- Project initialization creates manage.py, settings, URLs, etc.
- MVC pattern enforcement
Framework Positioning Analysis
Next.js Characteristics
- Frontend prioritized, minimal primitives
- No built-in auth, payments, database management
- Enables innovation through ecosystem flexibility
- Requires external battery sourcing
Laravel Characteristics
- Balanced frontend/backend priority
- Extensive built-in tooling ecosystem
- Livewire for websocket synchronization
- Inertia.js for React integration
- Happy path very effective, painful when deviating
Rails Positioning
- Heavy backend focus, high batteries inclusion
- MVC pattern enforcement
- Less frontend innovation compared to Laravel
Phoenix (Elixir) Features
- Rails-inspired but enhanced
- LiveView for frontend updates
- Built-in subscription/websocket primitives
- Less batteries than Laravel, more frontend focus than Rails
Framework Ecosystem Patterns
Next.js Ecosystem Extensions
- Blitz.js: Next.js wrapper with RPC, auth, Prisma
- Epic Stack: Kent Dodds' Remix starting points
- Create T3 App: Curated Next.js starter with selective batteries
Composability Philosophy
- Unix Philosophy: Simple, compact, modular, extensible components
- JavaScript ecosystem most Unix-pilled language
- Ubuntu desktop: 1500-2000 packages default install
- Composable pieces allow swapping when better solutions emerge
Complexity Scaling Principle
- Best Tools: Codebase complexity scales with problem complexity
- Minimal starting points clearer for understanding
- Laravel provides most needs immediately vs Next.js gradual addition
- Framework-routed connections harder to trace than explicit connections
Multi-Dimensional Framework Spectrum
Primary Axes
- Frontend vs Backend Priority: How much focus each side receives
- Minimal vs Batteries Included: How many built-in solutions provided
Coverage Spectrum (Bare Metal to Users)
- Bare Metal → Database → Services/APIs → Client APIs → Frontend Framework → Design System → Users
- Convex: Database to Client APIs coverage
- Laravel: Partial database (ORM) to partial frontend
- Next.js: Primarily Client APIs and Frontend Framework
Framework Coverage Comparison
- Different tools cover different spectrum sections
- No single term adequately describes coverage variations
- "Complete stack" vs "completer stack" terminology inadequacy
Terminology Resolution Challenges
- Full Stack: Multiple interpretations possible
- Backend + Frontend integration only
- Batteries included comprehensive approach
- Spectrum position dependent
- Current terms inadequate for describing fundamental differences
- Need separate terms for minimal vs comprehensive approaches
- MVC pattern often implied with fuller stack frameworks
Proposed Solutions
- Retire "full stack" term due to ambiguity
- Suggestions from discussion:
- BF Stack: Backend-Frontend emphasis
- Center Stack: Middle-ground positioning
- Web Stack: Comprehensive web development
- Need clear terminology distinguishing minimal composable vs comprehensive integrated approaches
