AI summary by TwinMind
Prisma is removing Rust?
Theo - t3․gg
21m 48s
Prisma ORM Manifesto Overview
- Prisma releases new manifesto addressing key challenges, governance issues, and future vision
- Accumulated 3,000+ open issues and years-long backlog of preview features
- Priorities unclear, deadlines inconsistently met
- Major architectural shift: migrating core logic from Rust to TypeScript
Historical Context & GraphQL Legacy
- Prisma originally started as GraphCool - attempted database-to-GraphQL API converter
- During peak GraphQL hype, tried making database work with GraphQL (problematic approach)
- Realized value wasn't in GraphQL server provision but in database workflow management
- Tech debt from GraphQL legacy created chaos with Rust server + GraphQL + TypeScript layers
- Rust abstraction built around GraphQL API focus, creating maintenance burden
Current Prisma Statistics
- Powers 547,000 GitHub repositories
- Serves 400,000+ monthly active developers
- 9+ million monthly npm downloads
- 200 releases completed
- 5,500 pull requests merged
- 7,500+ issues closed
First-Class Database Strategy
- Defining specific supported databases for focused development:
- PostgreSQL
- MySQL
- SQLite
- MariaDB
- Libsql (surprising inclusion)
- Recently added D1 and Turso (November 27th) relegated to community support
- Benefits:
- Prioritized bug fixes and performance improvements
- Innovation designed with these databases in mind
- Seamless integration and compatibility
- Non-first-class databases:
- Community extension points provided
- Custom database adapters supported
- Enterprise support available for paid customers
Issue Management & Community Engagement
- Acknowledging poor issue management (compared to Flutter's 12,928 open issues)
- Committing to organizing backlog, closing stale issues
- Using automation to scale community engagement
- Partnership with Dosu for issue triage
- GitHub as primary platform for all communications
- Monthly AMA sessions planned
- Community prioritization through upvotes and comments
Preview Feature Lifecycle
- Cleaning up process from early features to generally available
- Many features stuck indefinitely in preview status
- Implementing predictable lifecycle management
Core Architecture Migration: Rust to TypeScript
- Major Change: Migrating Prisma's core logic from Rust to TypeScript
- Historical limitations:
- Rust engine opaque to TypeScript-focused community
- Limited community contributions
- Deployment restrictions
- Performance issues
- Reliability problems
- New TypeScript core benefits:
- More accessible to TypeScript developers
- Extensibility built into design
- Plugin architecture focus
- Community can address issues directly
- Approachable codebase for contributions
Performance Expectations
- No performance numbers available yet
- Expectation: potential performance improvements despite slower language
- Ryan Carniato principle: rewrites often faster due to accumulated knowledge
- Database bottlenecks typically I/O and query management, not CPU-bound
- Architecture improvements may yield significant performance gains
Community Contribution Philosophy
- JavaScript as "working class language" - forgiving, easy to pick up
- Large pool of conversant developers
- Patch-package capability for quick fixes
- Ability to debug, fix, and modify dependencies
- Rust rewrites create contribution barriers for web developers
- Concern about similar issues with other Rust-based tools (Turbo Pack, RS Pack)
Guiding Principles
- Developer-first approach
- Focus on quality
- Open and transparent operations
- Collaborative development
- Continuous improvement
- Accountability: "call us out" if falling short
Sponsorship & Bias Disclosure
- Prisma continuing sponsorship despite creator's critiques
- Willingness to collaborate with critical voices
- Future sponsored content planned
- Transparency about financial relationship
