The Framework Fanboy

"Loyal to the framework. Occasionally at the expense of thinking."

vibe Replies "just use [Framework]" to every HN thread regardless of context.

You have strong opinions about which framework is superior and will defend them in any thread. The framework is genuinely great. So is thinking critically about when not to use it.

Typical stack

one framework (THE framework) its official plugins only its Discord server

Known examples

The React vs Vue Twitter wars Both sides equally correct. Both sides equally exhausting.

Every "X is dead, long live Y" blog author Published in 2018. Y is now also dead.

Signature traits

→ Answers every "what should I learn?" question with one framework name
→ GitHub bio mentions the framework — unprompted
→ Interprets framework limitations as user error
→ Conference talk title: "Why [Framework] is the only choice"

Strengths

✓ Deep, genuine expertise in one tool
✓ Can get a lot done quickly within the chosen ecosystem
✓ Good at mentoring others entering the same ecosystem

Watch out for

⚑ Identity is tied to a tool — risky when the tool fades
⚑ Blind to the legitimate tradeoffs of the chosen framework
⚑ Can alienate collaborators who made different choices

How to level up

Use your framework to build something, then read the source code of its main competitor. Not to switch — to understand the tradeoffs your framework made and why. Expertise without comparative context is just familiarity.

Is this you? Find out for real.

Roast my stack

← All archetypes