Your Framework Is Wrong (And Here's Why Mine Is Perfect)
Whatever framework you’re using, you made the wrong choice. Let me explain why my framework — which I just learned last week — is objectively superior.
The Scientific Analysis
I spent 48 hours comparing frameworks using rigorous methodology:
- Reading Reddit threads
- Checking GitHub stars
- Watching YouTube hot takes
- Asking Twitter/X
My conclusion: [framework I’m currently using] wins.
Framework Tier List
| Tier | Framework | Why |
|---|---|---|
| S | The one I use | Superior architecture |
| A | The one I used last year | Acceptable |
| B | The one my friend uses | He’s usually wrong |
| F | React | Too mainstream |
| F | Vue | Not mainstream enough |
| F | Angular | Obviously |
| F | Svelte | Hipster bait |
| F | Solid | Svelte for hipsters |
| F | HTMX | Just write HTML then |
| F | jQuery | Still works in production somewhere |
Why React Is Dead
React is dead. I’ve been saying this since 2019. Any day now.
// React (ancient, dying)
function Component() {
const [count, setCount] = useState(0);
return <button onClick={() => setCount(count + 1)}>{count}</button>;
}
// My framework (futuristic, alive)
function Component() {
const [count, setCount] = useMyFrameworkState(0);
return <my-button on:click={() => setCount(count + 1)}>{count}</my-button>;
}
See? Completely different paradigm.
Why Vue Is Dead
Vue has this thing called “Options API” and also “Composition API” and people argue about which one to use.
In my framework, there’s only one way to do things: my way.
Why Angular Is Dead
Angular is maintained by Google. Google also made Google+, Google Wave, Google Reader, and Google Stadia.
I rest my case.
Why [New Shiny Thing] Will Win
I saw a tweet about [new framework] and it has:
- 847 GitHub stars (growing!)
- Created 3 months ago (fresh!)
- One maintainer (focused vision!)
- No documentation (self-explanatory!)
- Breaking changes weekly (actively developed!)
This is the future. I’m rewriting everything in it. Again.
My Migration History
2015: jQuery → Angular 1
2016: Angular 1 → React
2017: React → Vue
2018: Vue → React (came crawling back)
2019: React → Svelte (hype train)
2020: Svelte → React (lol)
2021: React → Next.js (same thing?)
2022: Next.js → Remix (David Khourshid tweeted about it)
2023: Remix → Solid (conference talk made sense)
2024: Solid → HTMX (ironic contrarianism)
2025: HTMX → React again (Stockholm syndrome)
2026: React → Whatever's trending right now
I’m a versatile engineer.
The Real Framework Comparison
Lines of code to show "Hello World":
jQuery: 1 line
React: 15 lines
Angular: 47 files
Vue: 7 lines
Svelte: 1 line
My Framework: 1 line (but better)
The Framework Checklist
Before choosing a framework, ask:
- Did I already decide before doing research?
- Will switching justify rewriting everything?
- Can I put it on my LinkedIn?
- Does it have a logo I can sticker on my laptop?
- Will it be deprecated by the time I learn it?
If yes to all: perfect choice.
Conclusion
Use whatever framework I’m using this week. By the time you learn it, I’ll have moved on, but that’s not my problem.
XKCD 927 shows standards proliferating. Frameworks are the same but with more npm packages.
XKCD 1768 shows how I feel when someone criticizes my framework choice. How I feel when criticizing theirs: “reasonable discourse.”
Dilbert captured it: “We need to pick a framework.” “Which one?” “Whichever one I can expense a conference trip for.”
The author has “React Expert” in their LinkedIn bio but hasn’t used React in 2 years.