Back to journal
·2 min readVue.jsVueFrontendJavascriptFrameworkSingle File Components

Things I Love About Vue

Why Vue stuck for me after a student social network project in 2018. SFCs, CLI, Vuex, and a community that isn't owned by one company.

ShareCopy failed

My first Vue project was a student social network in 2018, last year of studies. I needed something I could learn fast and still ship. Vue won over the alternatives I skimmed.

I'd been writing vanilla JS. A framework felt like a big step. Vue didn't punish me for starting small.

You might disagree with everything below. That's fine.

Virtual DOM
Same idea as other frameworks, still useful. Vue figures out what changed and patches the DOM without you micromanaging every node.

Vue CLI
Scaffolding a webpack project used to be painful. vue create walks you through presets interactively. Babel and ESLint out of the box if you want them.

Single file components
Most Vue code I write lives in .vue files: template, script, style together. When a component gets huge, that's a hint to split it. Scoped styles keep CSS from leaking sideways. The SFC format is valid HTML5, which still makes me oddly happy.

Vuex
Centralized state when props start duplicating everywhere. Mutations are predictable. Pinia replaced it for many of us later, but Vuex taught me how to think about app-wide state.

Not one corporation
Evan You started it, community grew it. No single vendor roadmap to guess at.

Vue's ecosystem grew a lot since 2018. I still reach for it on new personal work. Your mileage may vary, but it's earned a permanent slot in my toolbox.

ShareCopy failed