October 6, 2026•5 min read

When You Pick a Framework Just to Look Different

The last time you chose a new framework or library, was it because your problem needed that tool, or because it sounded cool and few people around you were using it? That question is uncomfortable. Technology decisions are often made for reasons that never appear in any technical document.

Read in Indonesian

Be honest for a second. The last time you chose a new framework or library, was it because the problem in your project needed that tool? Or because the tool was trending, sounded cool, and not many people around you used it? 🤔

That question is uncomfortable to answer. Technology decisions are often made for reasons we never write into any technical document. The real reason is simpler and more embarrassing: you wanted to look different.

Key takeaways

Some technology decisions are made not for technical reasons but to look different from everyone else. That motive is expensive: time burns on hopping around without depth, working together gets hard when only one person understands the tool, and slowly you become someone who belittles other people's choices. A tool is not a substitute for identity, because what earns respect is the work and the thinking. Choosing an unusual technology is still legitimate, as long as the reason is technical and you can explain the trade-off without emotion.

So, here is the confession

My journey started with Angular, back in school. The reason was innocent. Plenty of tutorials online covered Angular, mostly from The Net Ninja. Then React, still in the class component era. Up to that point everything made sense, because it followed the material available.

The problem started at the next step. Moving to Vue was not because Vue was better for the needs at hand. The reason was wanting to be anti-mainstream, to differ from friends on React and, honestly, to feel superior. No benchmark, no trade-off comparison. Just a wish to be the one who doesn't follow the current.

The same pattern showed up again with Nuxt 2. People around me used Next, so the choice fell to Nuxt. Again, to stand apart. CSS was the same story. I was proud of indent-based SASS, the kind written with indentation and no braces. Why? It felt cooler. Plain CSS or SCSS felt meh, even though the final result in the browser is exactly the same. 😅

Why do we fall into the trap so easily?

There is one thing we forget: while still learning, we have no big results to be proud of yet. No product used by many people, no system that has survived for years. But we still need something to wear as an identity, and the stack is the easiest shortcut.

Think of it like picking a club jacket. You may not be any good on a motorbike yet, but the jacket already makes you look like one of the crew. A stack works exactly like that. Just mention a slightly rare tool, and it sounds like you understand more.

The online environment speeds this up. On Discord, on Reddit, and in group chats with developer friends on campus, there is the feeling of belonging to a small group that knows better. That feeling is very pleasant. There is a little recognition every time you say, "ah, I don't use that one". And pleasant things, naturally, make you want to repeat them.

Check yourself for a moment

Now it is your turn. Recall the last tool decision you made, whether a framework, a CSS library, or a tool for build. Then ask yourself honestly: why did you pick that?

Have you ever compared at least two options against clear criteria? Can you explain the weakness of your choice without feeling attacked? Or is the answer just, "well, it looked cool"?

Don't rush to a conclusion. Just answer in your head first, slowly. The answer may not be as bad as you think, but it may also look a lot like the confession above.

What is the bill, then?

A choice built on status is not free. The bill arrives slowly, and usually stays invisible until it piles up.

First, time is spent hopping around. Every framework switch starts at the surface again: learning routing, learning how state is handled, learning folder conventions. You end up knowing a little about many things but never really good at one. Deep experience takes time in one place, not ten.

Second, working together gets hard. If you are the only one who understands the tool, everyone else who touches that code has to learn from zero. A choice that felt different and cool turns into an obstacle for other people.

Third, and this is the worst part: slowly you become the person who belittles other people's technology choices. "Oh, still using that?" A small sentence like that sounds trivial, but repeated often enough, it narrows how you see things. That person's choice may have had a much stronger reason than your own. 😬

So what did I finally realize?

A tool is not a substitute for identity. It became clear, slowly, that people are not valued for the framework name on their CV. What is valued is the work and the thinking: how you break a problem apart, how you weigh options, how you explain a decision to other people.

The proof came later, as it usually does. After Svelte, then migrating to Nuxt 3, briefly trying TanStack and Astro but getting stuck at the how-to guide, and finally landing on Nuxt 4, what carried over was not API recall for each one. What carried over was the thinking. At the current job, everything is vanilla. 😭

No special directive, no compiler helping out. Just a basic understanding of how the web works. And there you can see clearly which knowledge sticks and which was only a name.

CSS ended the same way. From Bootstrap to Tailwind, briefly PicoCSS out of curiosity, back to Tailwind. Later I realized PostCSS was enough, and now it is plain CSS. After going that far around, the finish line turns out to be what I once called meh. 🙃

So is choosing differently wrong?

No. This is the important part, so don't misread it. Choosing differently is allowed, and often right.

If a rarely used tool really is the best fit for your problem, use it. There are only two conditions: a real technical reason, and a trade-off you can explain without emotion. If you can say, "this is faster for this case, but the community is smaller, and that is the risk", your decision is healthy.

So the mistake is not the choice. The mistake is the motive. The same tool can be a good decision or a status decision, depending on why you picked it.

Closing: relax, we have all been there

Thinking back, the journey is a bit funny. Going around Angular, React, Vue, Nuxt, Svelte, and back to vanilla, only to realize that what you were looking for was never the most different tool. It feels like riding around the city switching minibuses, when home was a five-minute walk. 😂

So next time a new framework trends on Reddit or Discord, hold your thumb for a moment. Ask first: do I need this, or do I just want to look different? If the answer is the second one, that's fine, we have all been there. What matters is being honest with yourself first, then npm install. ☕

Get better at shipping code.

Join the other developers getting tech updates, tips, and relaxed tutorials in their inbox every week.

Stay in the loop

Tech updates, coding tips, and relaxed insights straight to your inbox every week.

No spam. Unsubscribe anytime.

Read next

See all

For developers who learn by struggling

© 2026 Inva.dev.