AI summary by TwinMind
The First Post-React Framework Just Launched
Theo - t3․gg
20m 46s
Introduction and Background
- Solid Start 1.0 release - "the shape of Frameworks to come"
- Ryan Carniato praised as solid creator who knows other frameworks exceptionally well
- Phenomenal source of info on ecosystem, not just solid/signals
- Release represents 3 years of development: multiple rewrites, two beta phases, significant learning
JavaScript Framework Evolution Context
- Server rendering role growing in JavaScript for performance/optimization
- Everything points to leveraging server more
- Technology getting harder to start with - webpack configs now require server compatibility
- Need for solution: easy to start, not overly opinionated, appeals to everyone without fracturing ecosystem
- Vite 2.0 showed the way but still required additional tooling layers
Tooling Stack Architecture
- Base layer: ES build and rollup
- Vite built on top of base layer
- Nitro (next generation server toolkit) built on top of Vite
- Vinxi (full stack JavaScript SDK) as top layer
- Solid historically early consumer of these emerging technologies
- Layered approach necessary for frameworks like solid start to be viable
Solid Start Core Philosophy
- Designed first and foremost as a starter, not comprehensive framework
- Minimal starting point: 5 kilobytes minified JS + gzip for hello world
- Scales up/down based on usage - progressive enhancement approach
- No mandatory conventions - adopting provided ones gives best experience
- Pay only for features you actually use and need
Routing Architecture Innovation
- Bring your own application router approach
- File system routing available with similar convention to Nuxt
- Parameters passed via array syntax
- Parentheses for route groups, named index routes, breaking nesting
- Plus (+) prefix for routing files - sorts alphabetically to top of file tree
- File system configuration passed to application for any router choice
- Routes exportable as components for incremental adoption
Route Configuration System
- Export const route for custom route config
- Automatic lazy wrapping of default exported component
- Match filters for parameter validation (e.g., ID numbers only)
- TypeScript satisfies for route definitions
- Configured routes callable anywhere with custom types
Progressive Enhancement - Server Functions
- Built as single page app framework first
- Every feature designed to work with existing libraries
- Pioneered server functions in early 2022 (adopted by other frameworks)
- "Bling" era reference - early server function experimentation with Tanner/Ryan
- Server functions: write server code anywhere, compiler creates endpoint + replaces with fetch
Use Server Implementation
- Adding "use server" to function makes it server-only execution
- Works as RPC from client or natural server calls
- Transparent from TypeScript perspective
- Fits into existing APIs like fetches and TanStack Query
- Advanced serialization support: async iterables, streams, promises
- Smart bundler handles response bundling and client parsing
Performance Optimizations
- Single file mutations with solid's router API
- Server starts fetching next page data after update
- Streams back on same response with client handling redirects
- Parallelized local and cache patterns
- Non-blocking async eliminates unnecessary waterfalls
- Server-driven approach: immediate invalidation response, then new data stream
Comprehensive Feature Set
- Client render mode, server-side rendering, static site generation
- Out-of-order streaming, optimistic UI, key-based cache invalidation
- Progressively enhanced forms, API routes
- Parallelized nested route data fetching
- Single flight mutations, islands, suspense transitions
- 13 modern full-stack web development concepts integrated
Ecosystem and Community
- Framework designed for builders with opinions
- Meta frameworks building on top: create-jd-app, Media Kit
- Create-jd-app: similar to create-t3-app but solid-based with tRPC
- JD created original solid bindings for upload thing
- Healthy ecosystem signal from community tooling development
Acknowledgments and Philosophy
- Grateful to contributors, open source projects (Vite, Vinxi, Nitro)
- Sponsors: Netlify, Chrome, JetBrains
- Emphasis on "choosing better over convenient"
- Ryan Carniato streams Fridays, discusses other frameworks extensively
- Framework author who spends more time discussing other frameworks than own
