Model-config web apps: describe the app in configuration instead of writing code. Built on Polars and DuckDB.
The Rosetta Stone of Web Frameworks
Every Framework Is Just Config
We've proven it. Every web framework, every paradigm, every architecture - they're all the same patterns with different syntax.
This directory contains the proof: every major framework and paradigm expressed as DBBasic config.
Traditional MVC Frameworks
Rails in Config
- 50,000 lines of Ruby → 200 lines of YAML
- ActiveRecord, ActionCable, Sidekiq - all just config
Django in Config
- 10,000 lines of Python → 200 lines of YAML
- Models, views, signals, Celery - all just config
Laravel in Config
- 75,000 lines of PHP → 180 lines of YAML
- Eloquent, Livewire, Horizon - all just config
Spring Boot in Config
- 100,000 lines of Java → 200 lines of YAML
- JPA, Security, WebFlux - all just config
Modern JavaScript Frameworks
Next.js in Config
- 50,000 lines + node_modules → 150 lines of YAML
- SSR, SSG, ISR, API routes - all just config
Express in Config
- 10,000 lines + npm chaos → 100 lines of YAML
- Middleware, Socket.io, Passport - all just config
Advanced Paradigms (What MVC Couldn't Handle)
Actor Systems in Config
- Erlang/Elixir OTP patterns
- Supervisors, GenServers, message passing
- What Rails/Django couldn't express
Microservices in Config
- Service mesh, API gateways, distributed tracing
- Kubernetes, service discovery, circuit breakers
- The distributed systems Rails avoided
Functional Reactive in Config
- Streams, observables, pure functions
- Redux, RxJS, event sourcing
- The paradigm MVC never understood
The Universal Patterns
After mapping every framework to config, clear patterns emerge:
Every Framework Has:
model: # Data structure
routes: # URL handling
views: # Presentation
logic: # Business rules
external: # Integrations
The Only Differences:
- Syntax: Ruby vs Python vs JavaScript vs PHP
- Words: Controller vs Handler vs View vs Component
- Culture: "Convention" vs "Explicit" vs "Functional"
What This Means
For Developers
- Learn patterns, not frameworks
- Config is the universal language
- Switching frameworks = changing config
For AI
- Can generate ANY framework from config
- Can translate between frameworks instantly
- Can see patterns humans miss
For DBBasic
- One config format rules them all
- Generate optimal implementation
- No framework lock-in
The Manifestos
The DBBasic Manifesto
How we accidentally ended software development.
Config-Driven Development
The evolution from code-driven to config-driven.
The Racing Analogy
Why the industry built Formula 1 when we needed LEGO.
The Proof
These configs aren't theoretical. They're functional specifications that:
- Document what each framework actually does
- Prove they're all the same thing
- Enable AI to generate any framework
- Define the universal meta-framework
Example: The Same App in Every Framework
# This config...
model:
users: [id, email, name]
posts: [id, user_id, title, content]
routes:
GET /posts: list_posts
POST /posts: create_post
# ...generates:
# - Rails: 50+ files, 5000+ lines
# - Django: 40+ files, 4000+ lines
# - Next.js: 30+ files, 3000+ lines
# - Laravel: 60+ files, 6000+ lines
# - Spring: 100+ files, 10000+ lines
#
# Or with DBBasic: Just runs. 402M rows/sec.
The Revolution
We didn't create another framework. We proved frameworks are unnecessary.
Everything is config. Always was.
"The best code is no code. The best framework is no framework. The best architecture is config."
Welcome to the post-framework era.